Database Users

Galaxy Tab GT-P1010 (WiFi Only) NooB Guide

Galaxy Tab GT-P1010 NooB Guide - Last Revised 2012-02-29
2013-03-09 - SEE POST 9 FOR IMPORTANT INFORMATION
Revisions
2012-02-27 - Initial Publication
2012-02-29 - Added Firmware Download, Thread Consolidation, Custom ROM's, Flashing Stock Firmware and Q&A Section(s)
Post Summary
In this thread I will attempt to outline the details I know of regarding the Galaxy Tab GT-P1010. I feel this is a necessary thread because this device is NOT the same as the various other devices that garner so much attention within this forum and I personally experianced quite a difficult time searching to find the questions to my answers as they releated to this device in particular. While it is my opinion that this device should have it's own sub-forum, I do not believe it is popular enough. This said I feel that it is a fairly solid device and if you are like me, you are somewhat lost in in finding the approriate information. Hopefully this thread will be informative and popular enough that it may get stickied so us lowly 1010 users can find the information they are looking for. I am an active XDA member and will do my best to keep this thread updated as new information & techniques become available. If you see some information that you feel should be included do not hesitate to bring same to my attention and I will update the OP's accordinglly. These Instructions are for use on Windows machines even though I personally use a Mac. If you are in the same boat, I recomend running windows within a Virtual Machine (VM). I use Parallels but VirtualBox is a free alternative. Mac and or Linux only instructions may follow at a later date, but honestly a majority of users use Windows so I'm starting there. Without further a do, let's get started.
GT-P1010 Device Specifications
The GT-P1010 is also know as the "Wi-Fi Only" 7" Galaxy Tab. It differs from a majority of the devices in this forum because it has NO 3G or cellular capabilities. The hardware of the device is also different enough from the 3G/Cellular versions, that the Development going on for these other devices will NOT work for it. The GT-P1010 is unfortunately considered a "forgotten" device and even Samsung has seemingly abandoned providing updates for it. This is particularlly evident within the United States (US), however other Countries, speciffically the United Kingdom (UK) have been seeing updates. For the record I am the owner of a US version and this guide was written using my experiance on that device.
A complete list of specifications can be viewed from Samsung's US Website HERE
MD5 Sums
When downloading files from the internet is extremly important that you verify the download was complete and not corrupted. Insuring this can avoid troubleshooting issues that may simply be because of a bad file. All files available from this post will have an MD5 sum next to them. To verify that your file is EXACTLY the same as the file on the server you will need to run it through an MD5 checker. These checkers are available freely over the internet and Mac OS X even has one built in. I'm not going to make this post about how to run these programs but have included a few links below to get you started. A complete explanation of MD5 Sums can be found at Wikipedia.
WinMD5Free
Drivers - Samsung KIES
In order to perform updates to your P-1010 you need to be able to communicate with the device via a USB cable. While there are stand-alone USB drivers available, I chose to install Samsung's "KIES" application so that I could see if any updates were being pushed directly from Samsung. The KIES program also offers additional functionality to allow you to sync various media on your device. This functionality may or may not be needed for all users but by installing the software you are also guaranteed that the drivers needed to communicate with the device are installed on your machine. The US Samsung KIES site can be accessed HERE but I have included a direct link to the latest Windows Version below.
Kies_2.2.0.12014_18_7 ---- MD5 Sum: 7116aa29ce9df3dc2e916128c9c0aa4c
Download the file and double click it to install KIES and the drivers to you system. Once this is acomplished running the program will present you with a screen similar to the one below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ODIN
ODIN is a utility that communicates with your device when it is in Download Mode (see below). This utility allows you to flash different firmware and other files to your Galaxy Tab. A screenshot of ODIN running is posted below.
To Run ODIN you will need to download and Un-zip the following file. Once this is acomplished you can run the program by simply double clicking the .EXE file "Odin3 v1.85.exe" which will be inside the un-zipped (extracted) folder. The program does NOT get "installed" and this section is just an overview of the tool. Additional steps on when to use it, and how, will be included in the appropriate sections below.
Odin3-v1.85.zip. ---- MD5 Sum: 414e3af7c4c01e21527aeaab65e68a75
Download Mode
Initiating Download Mode
To communicate with ODIN the device needs to be placed into Download Mode. This is accomplished (from an OFF condition) by holding the Volume Down button + the Power Button at the same time until Download Mode is activated. I have found that the easiest way to do this is to press and hold the Volume Down button and then press and hold the Power Button. Download mode will activate within a couple of seconds and your device will indicate such by presenting you with the following screen. As soon as that happens you can release both buttons.
Exiting Download Mode
If you flash any updated files to your Tab using the procedures outlined below, the device will accept the files and reboot on it's own thereby exiting download mode. If you find that you have entered download mode when you did not intend to use ODIN to flash files, you can EXIT download mode by Holding the Power Button for about 10 seconds. The device will then turn off and when you turn it back on it will boot normally. This can be a little scary considering the warning stating "Do Not Turn of the Target". This warning can be ignored and it is actually telling you not to turn it off while files are being written to it.
Connecting Device to ODIN
To play it safe, I recomend that you try connecting your device to KIES FIRST just to insure that the drivers have been installed properly. If KIES can recognize the device then so can ODIN. Simply open KIES and connect the device to your computer via the USB cable. Once you see that KIES is communicating with the Tab you can close KIES and disconnect the Device from the USB. This will only need to be done once, again, just to make sure the communication is working. Once you are satisfied that it is ....
Run ODIN by double clicking the executable file as outlined above. Place the device in download mode as outlined above. Connect the device to the computer using the USB cable. You will then notice that ODIN has found and is communicating with your device because the ID:COM field will turn yellow and assign a COM port to your device. This COM port will vary by user so don't be alarmed if you personally don't see "COM5" as shown in the screenshot below. As long as this field turns yellow you are good to go.
Recovery Mode - Stock
A stock Tab has a built in recovery mode that will allow you to perform a factor reset on the device and other "maintenance". This mode is entered (from an OFF condition) by holding the Volume Up button + the Power Button at the same time until you see the Samsung Logo, then Release the Power button but continue to hold the Volume up button until Recovery Mode is activated and your device presents you with the following screen. As soon as that happens you can release the Volume Up button. Once Recovery is activated you can toggle through the menu items by using the Volume up & Volume down buttons. To execute a selection use either the Power OR Home Button. It is the Power button on my device but this apparently varies on some models.
Rooting
If you are here on XDA then you are probably interested in "Rooting" your device. Rooting has many advantages and certain Market Applications will only work if you have these Root Powers. The US version of the Stock GT-P1010 is currently running the Froyo version of the Android Operating System. A Gingerbread version has not been officially released and may never be. We will deal with upgrading to Gingerbread later in the Tutorial. For now, if you want to Root your device running Froyo (My device had Build: Froyo.UEKC6), you can follow these steps:
1. Download the application Z4Root from the following link:
Z4Root.1.3.0.zip ---- MD5 Sum: 077974421412b25089289acdc763b1c1
2. Unzip the archive to Extract the file : "z4root.1.3.0.apk"
3. Connect your Tab to the PC and initiate "Mass Storage Mode"
Connect USB Cable
Drag down Status Bar and Click "USB Connected" under the ongoing tasks
Click "Turn on USB Storage"
Your device should mount and be available as a Removable Drive in Windows
4. Copy the .apk file from step 2 to your device
It doesn't matter where you put this file. Just remember where so you can find it in the next step(s)
The easiest place would be the "root" of the Removable Disk
5. Enable "Unknown Sources" on your Tab
Settings >> Applications >> Check Unknown Sources Box
6. Enable "USB Debugging" on your Tab
Settings >> Applications >> Development >> Check USB Debugging Box
7. Install Z4Root
Use any "file explorer" program on the Tab. You should have an application called "My Files". It will work fine
Navigate to the .apk file you put on the device in Step 4
Click the .apk file
Click Install
Application will install and you will have a Z4Root Icon in your app drawer
8. Setup Z4Root
Click the Z4Root Icon
You will be presented with two (2) Options. Temporary Root & Permanent Root
I chose Permanent Root but you could "try" it first if you like
In my case the device re-booted and I was rooted.
To test this I installed an application called Titanium Backup (see next Section).
Note: The Z4Root Icon will remain and if you open it again you will be given the option to"Un-Root".
Titanium Backup
Titanium Backup is a GREAT program that lets you backup all your applications as well as the user data that is used by them. For example your game progress, high scores, ETC. Titanium Backup REQUIRES Root access and in my opinion is reason enough to Root your device. There is a Free as well as a Paid version of this application. Let's install this program to verify that we have in fact "rooted" our device.
Installing and Checking for Root
Go to the market and search for Titanium Backup
Give the free version a try just to confrm Root. Simply install it from the market.
Once installed open the application and you should be presented with a dialog box stating that "Titanium Backup is requesting Super User Permissions".
Click allow and follow any on-screen instructions
You will eventually get to an "Overview" screen and should see that Root Access has a Green Checkmark next to it and that BusyBox was installed from the app.
Congratulations you are now rooted
Backing up Files
To backup your applications and user data using Titanium Backup follow the steps below:
Open Titanium Backup and click the Backup/Restore Tab near the top of the screen
A list of the applications installed on your device will appear
Click the Settings Drawer Hardware Key
Click Batch
Under the Backup section on the next screen click Run next to "Backup all User App + System Data"
On the next screen Select the applications you want to backup, They are ALL selected by default.
Make sure the "Pause Active App's" radio button is selected
Click "Run the batch operation" button
Congratulations. You have just performed an application Backup!
Saving your backup to your computer
There is no reason performing a backup if you are just going to leave it on your device. Obviously if something catastrophic were to happen, you would lose the backup as well. The backup files are located in the /sdcard/TitaniumBackup directory.
Initiate "Mass Storage" as outlined in the Rooting Section above.
Once the device is mounted navigate to the TitaniumBackup directory. Note: When mounted to the PC, the /sdcard directoy is the one mounted so TitaniumBackup should appear in the root of the Removable Disk.
Copy the entire TitaniumBackup Directory to your PC
You now have a folder that can be restored to your device allowing you to restore your applications without re-downloading them from the Market.
Remember to copy this folder to your computer after perfoming any future backups.
Restoring your applications
To restore your applications and user data using Titanium Backup make sure that the backup containing the files you wish to restore is located at /sdcard/TitaniumBackup and follow the steps below:
Open Titanium Backup and click the Backup/Restore Tab near the top of the screen
A list of the applications installed on your device will appear
Click the Settings Drawer Hardware Key
Click Batch
Under the Restore section on the next screen click Run next to "Restore missing apps with data"
On the next screen Select the applications you want to Restore, They are ALL selected by default.
Decide if you want to restore just the app, the app and it's data or just the data by clicking the appropriate radio button
Click "Run the batch operation" button
Follow the prompts to install each application
Congratulations. You have just perfored a restore
Note: Once we get into flashing custom Rom's in the sections that follow, sometimes restoring application "data" can be problematic. If you flash a new firmware or Rom and are experiancing issues with an application after restoring it's data, this may be the reason.
Custom Recovery - ClockWorkMod
In the section above we explained about the System Reovery that was built and installed by Samsung. This is great for restoring your system to an out of the box (OOB) condition but not for much else. In order to flash custom Rom's and perform Nandroid Backups we will need to replace the "stock" recovery with a Custom version. ClockWorkMod (CWM) is the recovery of choice for a majority of users and while there are "others" out there, only CWM has been made available for our devices. A Nandroid backup is an exact copy or "image" of your system and can be used to restore your system to the exact state it was in at the time you made the backup. So, lets get to installing CWM.
You will need to download the following file:
Skin1980_P1010_CWM-RECOVERY-BETA-1 ---- MD5 Sum: ca14360ee5f1eebd0efaec5adc77940e
Note: This file is only to be used if you are running the Froyo Version of Android
Using the information above put your device in Download Mode and connect it to ODIN
click the PDA button in ODIN and navigate to the file you just downloaded
Make sure your ODIN screen is setup and matched the screenshot below:
Click the "Start" button and watch your device and the "Message" section of ODIN. You will see some some text in the message center and your screen will show a progress indicator.
Once this completes your device will re-boot. It may boot directly to your new ClockWorkMod OR it might boot back into your operating system.
If it boots to the operating system you can get to CWM using the same procedure outlined in the "Stock" recovery section above. Volume up + Power.
Make sure you are booted into CWM and see the screen shown below:
Once you are in CWM the Volume Up / Down buttonas re used to navigate through the menu choices and the Settings Drawer Hardware ley is used to select an option. The Back hardware key also functions to go back to the previous menu but all screens also offer a "Go Back" choice. If you click the Power Button and are presented with a blank screen simply click it again and CWM will come back up. Now, lets make out first Nandroid Backup!
Making a Nandroid Backup
Navigate and Execute the "Backup and Restore" menu item
Navigate and Execute the "Backup" menu item
Sit back and wait for your backup to complete.
A progress indicator as well as some text will be flashing across the screen
When it completes you will see .. "Backup Complete"
That's it! Congratulations!
Saving your backup to your computer
Again, as with Titanium there is no reason performing a backup if you are just going to leave it on your device. The CWM backup files are located in the /sdcard/clockworkmod/backup directory. Inside this directory you will see a folder that is named based upon the date and time you performed the backup. For Example 2012-02-27.21.57.14 means that the backup was created on February 27, 2012 at 21:57:14. This is UTC time so make sure you add or subtract your UTC offset to get to "local" time.
Initiate "Mass Storage" as outlined in the Rooting Section above.
Once the device is mounted navigate to the clockworkmod/backup directory. Note: When mounted to the PC, the /sdcard directoy is the one mounted so clockworkmod directory should appear in the root of the Removable Disk.
Copy the folder containing your backup to your PC
You now have a folder that can be restored to your device allowing you to restore your system to the exact sate it was in at the time of the backup..
Remember to copy any future backups to your PC as Well.
Restoring a Nandroid Backup
To restore your system to it's nacked up state make sure that the backup containing the Nandroid you wish to restore is located at /sdcard/clockworkmod/backup and follow the steps below:
Boot into CWM
Navigate and Execute the "Backup and Restore" menu item
Navigate and Execute the "Restore" menu item
Sit back and wait for your restore to complete.
A progress indicator as well as some text will be flashing across the screen
When it completes you will see .. "Restore Complete"
Navigate to and execute the "Reboot System Now" menu item
Your device will reboot and you will be restored to the exact state your system was in when you made the backup
Mounting Mass Storage in CWM
In some instances you may be faced with a system that won't boot which makes getting your Nandroid Backup put back on your device problematic. Don't fear. Using CWM you can mount the USB Mass Storage without the need to be running the operating system. Here's how:
Boot into CWM
Plug your USB Cable into your PC
Navigate to and Execute the "Mounts and storage" menu item
Navigate to and Execute the "mount USB storage" menu item
The Device will mount and you will have access to it from your PC
Copy your Nandroid Backup to the clockworkmod/backup folder
Go "back"
Go "Back"
Go to "backup and restore"
Restore your Nandroid
Reboot
Welcome back to a running machine!!
Credit and Thanks
While I have compiled all the files, tested them, generated MD5 Sums and written this tutorial based upon my experiance, it should be noted that other users are responsible for the actual Development. If you think I have done a good job and find this information usefull Please click my "THANKS" button. It is not necessary to thank me by witing a seperate post and by not doing so you keep this thread clean and easy to find the information that others may be looking for You should also visit the following users, find a post or two from them and THANK them as well. Without them none of this would be possible.
Skin1980 for his Development of ClockWorkMod for the GT-P1010
RyanZA for his Development of Z4Root
motafoca for his Development of ClockWorkMod for the KPI Firmware
Donations
While I enjoy tinkering with devices and trying new methods, doing so can be time consuming. Compiling and witing this tutorial took me a considerable amount of time. I have also convieniently placed all the required files on an Ad-Free, Fast Download server so you can get them quick and don't need to hunt around. Mediafire was my server of choice but it is NOT free. I pay a monthly service charge to host on the server and this will also insure that the files are available now AND in the future. If you like my work and feel that it has helped you, I would appreciate a donation as a token of your appreciation. Simply click the button below or the "Donate to Me" button under my Username. Anything you can spare will be appreciated and go toward keeping the file sharing up and running as well as keep me interested in generating more tutorials. Thanks in advance!
Questions or Comments
If you have any questons or feel that certain information could be added or clarified, feel free to post them. I will do my best to check this thread often and assist you as best I can. Valid questions will be answered and added to the Q&A post below.

Firmware and Kernel's for P1010
This section will contain a list and download links for the various Firmware's available for the GT-P1010. As noted above the US version has been getting no love from Samsung with regard to updates. This is a shame and makes no sense to me considering the UK version HAS been actively updated. With this said however many users have been "flashing" the UK versions to their US Tab's with success.
SamMobile Firmware Page
Latest Firmware
Europe Firmware
Middle East Firmware
Compliments of Mod2Xtreme.com
Forum Post Link
Firmware Direct Links
P1010XWKC1_OXX.rar ..... MD5 Sum: 95bd7437271f3bee6eacb017d0ef45a1
P1010XXKPG_P1010XEUKPG_XEU.zip .... MD5 Sum: 3b0f63ccb0b42643d953fcba472eb5f2
P1010XXKPI_XEUKPI_Android_2.3.6.zip .... MD5 Sum: 4d33426db6cecdb48568adecf10bc8fd
Kernel's
P1010ZHKF1-kernel.ZIP .... MD5 Sum: 6dc467ff92fc676c1f61e59e893493eb

Custom Rom's
2/29/2012
Currently there are no Custom Rom's available for the GT-P1010. A Developer named Motafoca is working on a port of Cyanogenmod and information regarding progress can be viewed in the following thread.
Motofoca's Cyanogen Port
Motofoca is a member of the MadTeam and they have their own forum which can be viewed HERE.
The only other "Non-Stock" alternative at this time is CleanRom developed by scrosler There is also a website dedicated to this ROM viewable HERE.
I used the term "Non-Custom" because the CleanRom is based upon a Stock Gingerbread European firmware. From the Website they did the following:
Removed Samsung Bloat!
ADW Launcher or TouchWiz Launcher!
95% AOSP Gingerbread themed
All Apps up to date!
De-Odexed
Zip Aligned

Flashing Stock Firmware(s)
Flashing Stock Firmware(s)
We have said that updated firmware for the US version of the GT-P1010 has NOT been actively provided by Samsung however if you look in Post 2 above you will see that all is not lost. The Europe version of this device has been provided with an update as late as January 2012. I would recommend (and really it was the reason I wrote this tutorial) that you perform ALL the steps above BEFORE flashing any type of Firmawre update/upgrade. This will not only give you experiance running the "tools" but it will allow you to perform the various back-ups in case anything goes "wrong".
Quite simply, Firmware is "flashed" to your device using ODIN. I have searched for a complete guide explaining the vaious sections of ODIN to no avail. Honestly I don't know when certain fields (PIT, CSC), ETC need to be populated and when they don't. I believe, but am not 100% sure that when flashing a brand new Firmware (for example from a US to European version) that the PIT, PDA and CSC fields need to be filled in and the Re-Partition radio button needs to be Checked. I have ALWAYS had the Auto-Reboot & F. Rest Time boxes checked, but again, I can't say why. It is my belief that if the Re-Partition button is checked, that it has the effect of "wiping" all partitions on the device.The only guide I have found is the following:
P1010-Flashingguide.pdf
It is probably a fair statement to make that if a Zip or RAR file you download contains a PIT or CSC file, then you probably need to included them in your flash. Keep in mind that I have experianced an issue where a seperate ZIP file was compressed inside an overall ZIP container. Always make sure that you not only extract the main downloaded file but that you also look inside the extracted folder for another ZIP file that may need to also be extracted.
I will provide an example of my experiance upgrading my US version to the latest UK version below.
Upgrading US Version to Latest Rooted UK Version
First, I must give full Credit to Taney for developing the instructions from This Thread. I followed them and experianced no significant issues. I will be re-creating a portion of them, expanding (clarifying) on some areas that I felt would give NooB's difficulity and then taking the instructions a step farther to upgrade to what is known as the "KPI" version of the Firmware which is the latest one Available. PLEASE make sure that you "Thank" Taney because without the instructions that he provided none of this would be possible.
A. Upgrade / Downgrade to the Latest Froyo Firmware
Place your Device in Download Mode and connect it to ODIN as outlined in the tutorial above.
Download the P1010XWKC1_OXX.rar file from the link in Post 2 of this thread and check the MD5 Sum
Extract this rar file to create a folder called "P1010XWKC1_OXXKC1"
Within ODIN Click the PIT button and navigate to the file "p1wifi_20110128_r10_00.pit" within the folder you extracted.
Click the PDA Button and navigate to the file "P1010XWKC1-REV03-ALL-low-CL946441.tar.md5"
Click the CSC Button and navigate to the file "GT-P1010-MULTI-CSC-OXXKC1.tar.md5"
Make sure the Re-Partition, Auto-Reboot and F. Reset Time buttons are CHECKED
Click "Start". ****** NOTICE THIS WILL WIPE ALL DATA ON YOUR DEVICE*****
When these steps are completed and the process running your ODIN screen should look like this:
When the process Completes your Device will Re-boot. The first Boot could take significantly longer than normal. Just wait and when you see the lock screen open it and enter the OS. At this point you may be experiancing what is known as a "boot-loop". Simply stated the device will keep re-booting and not allow you to do anything without throwing "force close" errors, In his tutorial Taney says that this may or may not happen. It did for me and the fix is in the next section.
B. Flash updated Kernel
To fix the effects of the boot loop you need to flash another file known as a kernel. Like I said I personally DID experiance the boot-loops and had to perform these steps. Since my overall procedure was successful, it is my recomendation that you do it whether you experiance the boot-loop or not. This decision is entirely up to you but you have my suggestion. To flash the Kernel perform the following:
Download the file file "P1010ZHKF1-kernel.ZIP" from the Kernel's section in Post 2 of this thread and check the MD5 Sum
Extract the ZIP file to create the folder "P1010ZHKF1-kernel"
If ODIN is still open replace the file in the PDA field with the file "P1010ZHKF1-KERNEL-eng.tar" from the extracted folder OR
If ODIN was closed open it, repopulate the PIT and CSC fields as outlined in Section A above and select the new file for the PDA field.
UN-CHECK the Re-partition check box
Power off your Tab. NOTE: If it is stuck in a bootloop I found that holding the power button down finally was able to shut off the device.
Start the device in Download mode and connect it to ODIN
If everything is set-up as outlined and ODIN has found your Device.. Press Start
When the process completes your device will re-boot and the ODIN screen will look like this:
At this point you should have a bootable Device and not experiance any further boot-loops. Your About Device Information should read as follows:
Firmware: 2.2.1
Kernel: 2.6.32.9 ([email protected]_24 #1)
Build: Froyo.XXKC1
C. Flash KPG Gingerbread update
In this step we will flash our first Gingerbread update known as the "KPG Version". Follow these steps:
Download the file "P1010XXKPG_P1010XEUKPG_XEU.zip" from the Firmware section in Post 2 and Check the MD5 Sum.
Extract the ZIP file to create the folder "P1010XXKPG_P1010XEUKPG_XEU"
If ODIN is still open replace the file in the PDA field with the file "P1010XXKPG_P1010XEUKPG_HOME.tar.md5" from the extracted folder OR
If ODIN was closed open it, repopulate the PIT and CSC fields as outlined in Section A above and select the new file for the PDA field.
UN-CHECK the Re-partition check box
Power OFF your Tab
Start the device in Download mode and connect it to ODIN
If everything is set-up as outlined and ODIN has found your Device.. Press Start
When the process completes your device will re-boot.
At this point you should have a bootable Device running Gingerbread. Your About Device Information should read as follows:
Firmware: 2.3.6
Kernel: 2.6.35.7 - CL749223 ([email protected] #1)
Build:GINGERBREAD.XXKPG
D. Reinstall ClockWorkMod
The steps above have had the effect of returning your device to stock and therefore the Recovery Partition was overwritten with the "stock" recovery. We need to re-install ClockWorkMod at this point.
Download the following file and check the MD5 Sum
Skin1980-P1010-NEW-CF-ROOT-GB.tar .......MD5 Sum: 1cab6775d572c416371c09f9c3654823
Put your device in Download Mode and Connect it to ODIN
Navigate to the File you downloaded using the PDA field
Leave the PIT and CSC fields BLANK and Un-Checked
Un-Check the Re-Partition Check Box
Click RUN
When the operation completes the device will re-boot
At this point you will have a Rooted KPG Version of Gingerbread with a fully Functioning ClockWorkMod Recovery. You may wish to stop here but reports informed me that the KPI firmware was faster. I decided to Install it as outlined blelow/
E. Flash KPI Gingerbread update
Before Installing the KPI Update I did the following:
From within the running system went to CWM application and opened it.
Granted the application Superuser Permissions
Used the application to "Re-Boot to Recovery"
Device Re-Booted into CWM and I performed a Nandroid Backup
While still in CWM "Wipe Data / Factory Reset" AND
Wipe Cache Partition AND
Wipe Dalvik Cache
Power Off
Your Device is now ready to recieve the KPI Firmware Update
Download the file "P1010XXKPI_XEUKPI_Android_2.3.6.zip" from Post 2 and Check the MD5 Sum
Extract the the file to create the folder "P1010XXKPI_XEUKPI_Android_2.3.6"
Start you Device in Download Mode and connect it to ODIN
Navigate to the file "P1010XXKPI_P1010XEUKPI_HOME.tar.md5" in the PDA Field
Leave the PIT and CSC fields Blank and Un-cjecked
Make sure the Re-Partition checkbox is Un-Checked
Click Run
While the program is running your ODIN screen will look like this:
When the Process completes your Device will Re-Boot and your About Device Info will be as follows:
Firmware: 2.3.6
Kernel: 2.6.35.7-CL882382 ([email protected] #1)
Build: GINGERBREAD.XXKPI
At this point I performed the following:
Went Through Initial Setup Screens
Powered Off Device
F. Re-Install ClockWorkMod AGAIN
Same as before. The procedure has wiped out our Recovery and we need to Re-install it. This time however we will use a different file beause I do not Believe the Skin1980 Gingerbread Version is compatible with the KPI Firmware. Luckily we have another Developer working on this Device. Please visit and Thank Motafoca for providing the following file:
madteam-cwm-p1010-kpi.tar .......MD5 Sum: f868e789245ec3dae87efaf2e30b1165
Put your device in Download Mode and Connect it to ODIN
Navigate to the File you downloaded using the PDA field
Leave the PIT and CSC fields BLANK and Un-Checked
Un-Check the Re-Partition Check Box
Click RUN
When the operation completes the device will re-boot
At this point you will have a Rooted KPI Version of Gingerbread with a fully Functioning ClockWorkMod Recovery.
G. Final Steps (Optional)
Opened CWM Application and Granted SuperUser Permissions
Rebooted to Recovery Using "Reboot Recovery"
NOTE: This version of CWM uses different button mappings. Volume Up / Volume Down to navigate and POWER button to Select
Mounted Device using Mounts / Storage and connected to PC
Put Titanium Backup files back on Device
Reboot System Now
Setup Date and Time
Connected to WiFi
Went to Market and Added Google Account
Waited for Account Sync to complete
Re-Enabled "Unkonon Sources"
Downloaded and Installed Titanium Backup
Ran Titanium Backup and Restored app's and data
DONE and running PERFECT !!!! Enjoy!!!
Donations
While I enjoy tinkering with devices and trying new methods, doing so can be time consuming. Compiling and witing this tutorial took me a considerable amount of time. I have also convieniently placed all the required files on an Ad-Free, Fast Download server so you can get them quick and don't need to hunt around. Mediafire was my server of choice but it is NOT free. I pay a monthly service charge to host on the server and this will also insure that the files are available now AND in the future. If you like my work and feel that it has helped you, I would appreciate a donation as a token of your appreciation. Simply click the button below or the "Donate to Me" button under my Username. Anything you can spare will be appreciated and go toward keeping the file sharing up and running as well as keep me interested in generating more tutorials. Thanks in advance!

Thread Consolidation and Links
The following Threads have been found and pertain strictly to the GT-P1010. If you find another thread that you feel should be included either link it in a post or PM me. I will review same and add to this section as appropriate.
[WIFI Only] [How-to] GT-P1010 Gingerbread Update ........ Thanks Taney
[CWM][RELEASE] Clockworkmod recovery for P1010 ....... Thanks Skin1980
Galaxy Tab p1010 tweaks ..... Thanks s2h2golf
[Tool / Mod] - CleanMOD 1.0.1 for GT-P1010 Gingerbread 2.3.6! Mod the Tab! ..... Thanks scrosler

Omg. G-R-E-A-T thread. Soo cool. Well, maybe we can cm on the tab, but a lot of developers are selfish

thank you for creating this guide!!
I got one of these for my daughter to play with and I was having a hard time figuring out what information pertains to her model.

Question and Answer Section
***** Reserved for Questions and Answers *********

2013-03-09 - I have been away from these forums for awhile now and apologize if I haven't been around to answer any questions. Just been too busy with other responsibilities. While I still own this device, I have moved on to another and have not kept up with development on the GTP-1010. I hope that many users have had success but I know from reading the posts that a few have struggled. Thank you to those that have attempted to assist in my absence. Honestly, without doing much with this device, I don't know how to answer some of the PM's I have received. This device was at the time considered "Legacy" in my mind and over 1 year later I don't believe anything has changed. With this said I will not be providing additional information or files and it does not make financial sense for me to continue paying for the "Pro" mediafire account. I will be canceling it today but have paid for it through 2013-04-01 at which time it will revert to a "free" account. I have no idea at this time what will happen to the links in my posts on that date but suggest that anyone interested, download everything before then. If time permits I will attempt to move everything over to a new server but I make no promises. The "free" version of Mediafire may still work but I vaguely remember paying for "pro" for a reason. I just don't remember why. Thanks for all the "thanks". I'm glad this has at least helped some people. Again, I appologize for not being around and for any issues with the links after April, 1 2013

******* One More for Good Measure ********

Bravo
Thank you for your hard work. Sent donation. Saved me hours of searching and coordinating the info. C'mon guys, how much time has this post saved you?

Hi i followed your instructions until i got to "Rooting" section.. the little problem issue i have is that the device i have doesn't have the Android Market..(i know i was shocked too) it has the Samsung Apps online but even that doesn't have the Titanium Backup App... any suggestions of how to install the Android Market? (btw love the instructions, nice and clear)

apolonetics said:
Hi i followed your instructions until i got to "Rooting" section.. the little problem issue i have is that the device i have doesn't have the Android Market..(i know i was shocked too) it has the Samsung Apps online but even that doesn't have the Titanium Backup App... any suggestions of how to install the Android Market? (btw love the instructions, nice and clear)
Click to expand...
Click to collapse
Sorry about the late response. Honestly this forum gets very little attention and I haven't been checking as often as I should.
That said ... I think you need to review post 4 which is an extension of the lessons learned in post 1. The firmware files ALL have the market built into them and following those steps should return you to a STOCK ROM. Make sure you backup any user files that you need before you begin. An internet search should allow you to find the .apk file for titanium backup. If you enable "unknown sources" in settings and get the app onto your device, clicking it should install the application. I'm not sure though if you finished the rooting step of stopped short or it. You NEED root to run Titanium,
Also, Keep in mind that as stated I performed these steps on a US version of the hardware and I don't offer that devices from other regions will be 100% compatible. But, from my research I believe most should be.
In summary, please provide me with additional details regarding your device and it's history. I'm sure we can get you squared away. There is always a Google App's package (GAPPS) that could be flashed to your device to get the Market but I am concerned about the fact that your's doesn't have it. This makes me think that without starting from a fresh ROM we would ultimately just be chasing our tails trying to troubleshoot other issues.

Thank you so much for replying.. i didn't think you'll reply to my post... but before i go to the next step.. i was playing around with it.. following your instructions on updating drivers and rooting etc... i then got stuck on "rooting" section hence me posting for help on getting the Titanium Backup... anyway i decided to upload couple of rugby videos so i can watch it later... i was in the middle of one video when all of sudden it stopped and turned itself off, i turned it back on and it stuck on the Samsung logo and it has been stuck on that since 24+ hrs ago after turning it on/off... on/off - i think i might have f'd it up...
I got it as a prize from a competition last year (2011) in Oct, and ever since i've been having problems with it.. let me know what other info you need me to provide!
much appreciated for the help!

THANKS SO MUCH! You made my day!
-Redbearded Tyrant
"Sic Semper Tyrannus"

apolonetics said:
Thank you so much for replying.. i didn't think you'll reply to my post... but before i go to the next step.. i was playing around with it.. following your instructions on updating drivers and rooting etc... i then got stuck on "rooting" section hence me posting for help on getting the Titanium Backup... anyway i decided to upload couple of rugby videos so i can watch it later... i was in the middle of one video when all of sudden it stopped and turned itself off, i turned it back on and it stuck on the Samsung logo and it has been stuck on that since 24+ hrs ago after turning it on/off... on/off - i think i might have f'd it up...
I got it as a prize from a competition last year (2011) in Oct, and ever since i've been having problems with it.. let me know what other info you need me to provide!
much appreciated for the help!
Click to expand...
Click to collapse
Honestly in order to support you I believe you should start from scratch. You should be able to get the device to download mode even if it is stuck on the Samsung Logo. Hold the power button until the unit turns off completely and then use the instructions to enter download mode. Then follow all the instructions in Post 4.
This will of course wipe your device totally clean so make sure you have everything backed up. Even though you can't get the system to boot you may be able to access your files by hooking it up to the PC. This is certainly true if you have already installed CWM. Look in the tutorial and find the section where I discuss "Mounts & Storage" from within CWM. This will allow you to copy off any important files. Then perform all the steps in Post 4.
That is really all I can offer as I don't know what you have done on the device to this point.

hai there.
i have few questions regarding upgrade to gingerbread.
my OS is 2.2.1 Froyo.DXKG1
if i want to upgrade my device to gingerbread P1010XXKPI_XEUKPI_Android_2.3.6, should i upgrade my device to the latest froyo (P1010XWKC1_OXX) then to gingerbread (P1010XXKPG_P1010XEUKPG_XEU) then to gingerbread (gingerbread P1010XXKPI_XEUKPI)??
or i can upgrade it straight away to gingerbread P1010XXKPI_XEUKPI_Android_2.3.6??
Thank you

Hi, i can't find your Post 4, are you able to post a link here please... ta

totihut said:
hai there.
i have few questions regarding upgrade to gingerbread.
my OS is 2.2.1 Froyo.DXKG1
if i want to upgrade my device to gingerbread P1010XXKPI_XEUKPI_Android_2.3.6, should i upgrade my device to the latest froyo (P1010XWKC1_OXX) then to gingerbread (P1010XXKPG_P1010XEUKPG_XEU) then to gingerbread (gingerbread P1010XXKPI_XEUKPI)??
or i can upgrade it straight away to gingerbread P1010XXKPI_XEUKPI_Android_2.3.6??
Thank you
Click to expand...
Click to collapse
Yes! This is what worked 100% for me so I recomend all the steps. The first upgrade to latest froyo has repartition checked which essentially gives you a clean slate. The seperate GB steps insure you end up with root. Good luck!

apolonetics said:
Hi, i can't find your Post 4, are you able to post a link here please... ta
Click to expand...
Click to collapse
Its the 4th post in THIS thread. "Flashing Fimware" section.

Z4L/Z4/Rockchip - Firmwares/ROMs/Root/TWRP & Performance Tweaks & Tricks

WARNING: I am not responsible if you use any of the following and for any troubles you may experience with your device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I recently got a Z4L and wanted to do a few things with it. After many days and nights, I am ready to share. I also wanted to consolidate an area for us to easily get items. I will add things from others if pertinent or greatly desired. Much of this will also apply to the Z4 and to other Rockchip Android TV Boxes (to a lesser extent).
This first section will entail some information, firmwares, apps, and performance tweaks and tricks.
The second section will have information on flashing firmware, ROMs, and recoveries.
The third section will have all the available tools for Rockchip boxes.
Z4 vs. Z4L
The Z4 and Z4L are essentially the same Android TV Box with a few minor differences. The Z4 has dual band WiFi, while the Z4L only supports wireless b/g/n. This is because the Z4 uses an Ampak AP6335 chip, while the Z4L uses a Realtek RTL8723. Does it matter? Yes. I have found that many firmwares and ROMs will work on the Z4L, however, all WiFi and Bluetooth connectivity is lost. And even other Rockchip Android TV Box firmwares sharing the same chip have had problems (e.g. USB ports no longer work, partial loss of remote functionality).
Another difference on the Z4L is OTG capability. While the port works for flashing, it will not work for any external devices when in the Android OS...
A final, possible, difference is that I think the Z4L only comes with 8GB of storage, but I could be wrong.
Firmware
This is the stock firmware for the Z4L. It was quite difficult to find, and was the only one I have come across:
Z4L Stock Firmware
Custom Firmwares
This is the Z4L stock firmware with enhancements. I have made some performance tweaks to help make the Z4L run smoother. Apps have also been added (with the exception of FolderMount), which I will have available in a separate section below.
In the slim version, I have taken out several apps I found unnecessary (e.g. Gmail, Calculator, etc.). Things you would normally leave to a smartphone or PC. While the firmware will be the exact same size as the stock firmware, rest assured it is slightly lighter:
Z4L Slim
In the lug version, I have not taken out any of the preinstalled apps. Instead, I have just added the same ones placed in the slim version. This will be a larger file size due in part to the additional apps, and the extra space I left for possible future modification needs:
Z4L Lug
Apps
Kodi
Kodi 15.2 RC PL
This is the beta that comes with a lot of the Android TV Boxes. It is preloaded with official and non-official add-ons. While it is suggests it is a 15.2 Isengard Release Candidate, the app settings in Android (and at least one Kodi updater app) will state that it is version 15.1.
Kodi 15.2 PL
What I have found on the Z4L is that I cannot update it. The Play Store gives no update option. Update apps for Kodi will attempt to update and fail to install, as will a manual download from the Kodi site. The only way I could update to 16.0 was by uninstalling 15.2 RC and then installing 16.0. I would lose all add-ons, and even a backup from Kodi will disallow restoring unofficial add-ons. Even if manually adding unofficial channels, I had problems getting them to work...
Kodi 16.0 PL
This is the latest (Jarvis) Kodi, and I have gone ahead and preloaded it with all the same add-ons from the 15.2 RC version:
Kodi 16.0 PL
ZDMC 16.0 PL
This is a software built on Jarvis. I have inserted all the preloaded add-ons from the 15.2 RC version in it. I am unsure what the difference is with Kodi. They look virtually the same, except for the logos and branding (since Kodi does not allow others to use their IP).
ZDMC 16.0 PL
Stock Apps
The only other stock app I thought would be of interest is the launcher. I actually prefer it to any of the others available. It may or may not work fully with other Android TV Boxes:
MyLauncher
Apps in Custom Firmwares
These are all the apps that come in the custom firmwares I created:
Added
Other Apps
FolderMount is an app that can help when you have little storage space. The only reason I have it here is because it does not come with any of the custom firmwares and will be needed for one of the performance tweaks and tricks:
FolderMount
Performance Tweaks & Tricks
Some of these tweaks or tricks may be dependent upon root. The Z4L comes prerooted, but others may need to obtain root first.
Speed Up
One of the best fixes I can recommend to help with any sluggish performance is to speed up your CPU cores. Download an app like Kernel Adiutor to give you as much access as possible. If you download something like No-frills CPU Control, you will only have access to the "Little" cores of the RK3368.
Open your app of choice and find the area that allows you to set the minimum and maximum states of the CPU.
Ensure that the "Big" cores are set to 1.5GHz for the maximum state.
Change the minimum state to 1.5GHz.
Do the same for the "Little" cores, where the maximum state should be 1.2GHz.
You can leave the governor as Interactive or change it to Performance.
Leave the I/O scheduler as "cfq" for daily use, use "noop" for benchmarks.
I have not experienced any type of overheating from these settings.
Maximum GPU Performance
If you want to get a bit more out of the PowerVR Rogue G6110 GPU, you can downsize your resolution. I use a 1080p TV, so I changed the Android OS resolution to 720p. Download something like NOMone Resolution Changer, or equivalent. A few items will have some larger writing even after the DPI change, but nothing that should deter you from keeping the setting.
Open your app of choice.
Set the resolution to something like 1280x720.
Change the DPI to (or around) 151.
Apply.
Some apps will ask if you want to keep the settings, and prompt you if you need another message in case something happens. With NOMone, this does happen. It also gives you the ability to reset to default settings if need be.
With the two above tweaks, I was able to get the multi-thread score to outperform an iPhone 5S in GeekBench. And in GFXBench, I was able to outperform a LG G4.
Internal/External Storage Swap
The greatest drawback of the Z4L is the 8GB of storage space. It can fill up quickly if you want to play games, or have hefty apps. You will need to download SD Fix and FolderMount. I have tried other apps like Links2SD and Int2Ext, but they do not work.
Open SD Fix and follow the instructions.
Reboot.
Open FolderMount.
Analyze the apps and see which have Data or OBB files, and are not grayed out.
Select them and make a pair.
You can select a USB flash drive if you do not want to use a micro SD card, but either way, ensure the source and destination sources are properly chosen.
SD Booster
It is probable that your internal storage and micro SD card are not optimized. Download SD Booster to change this and speed up your I/O abilities. Red means that you are definitely not optimized, yellow means you are operating at substandard levels, green means your are at the perfect level, and purple means you are operating beyond the perfect level.
Open SD Booster.
Select the internal or external storage.
Change the original value to a different one (i.e. 512, 1024, 2048, 8096).
Use the green checkbox to confirm the changes.
Use the green checkbox on the main window to implement the changes.
The Z4L's internal storage is in the red when first opening this program, so this will help somewhat. You may not get a huge jump in read or write speeds, but every little bit helps.
Developer Options
The Z4L does not have the ability to enable Developer Options natively. The "Build" section is not present. Download and app for Developer Options, I recommend the one from Andev.
Open your app of choice.
Click whatever button(s) needed to access Developer Options.
The one I have mentioned is part of the custom firmwares I created. The only caveat is that it will require you to sign into your Google account before proceeding.
Xbox 360 Wireless Controller
If you want to use a Xbox 360 wireless controller instead of a wired one or Bluetooth gamepad, you can! You will need a Xbox 360 wireless gaming receiver. Download USB/BT Joystick Center.
Open USB/BT Joystick Center.
Plug in the wireless receiver.
Click the button on the wireless receiver for sync.
Click the middle button of your Xbox 360 wireless controller.
Click the sync button located on the top of the Xbox 360 wireless controller.
Select the option to search for controllers on USB/BT Joystick Center.
Once the controller is recognized, immediately begin testing the buttons and whatnot or you may lose connectivity.
This is a bit finnicky, but it does work. The first couple times I could not get the controller to stay synced. Once it did stick, I tried it with Dead Trigger 2 and found that almost everything worked but the D-pad. Of course, I still had to setup the buttons.
Misc. Issues
Apps Not Working
Some apps can be downloaded but will FC when trying to open them. For this, I do recommend downloading the APKs from somewhere reputable and installing them with the file explorer.
Stock File Explorer
The stock file explorer is actually good, but it will not let you go to root ("/"). For this you will require something like ES File Explorer File Manager or Root Explorer. I found that whenever I would go to the Data folder on ES File Explorer File Manager (after selecting show Hidden Files), it would show it as empty. Whereas, Root Explorer would show everything. However, I have not been able to access my USB flash drive through Root Explorer, but can do so with ES File Explorer File Manager.
Stock Media Player
The stock media player plays most everything, and has built-in 3D capabilities. However, when trying to play some x265 files, there were problems. I would recommend installing MX Player to help with H.265 or VP9 codecs.
10-Bit Video Files
8-bit video files for H.265 or VP9 have no problems playing on these boxes. But when trying to play something that is 10-bit, it has nothing but major frame stutter, audio skip or silence. Until these codecs are made to not utilize so much CPU power, I do not think anything other than actual PC's will be able to play them properly.
External Webcam
It may be possible to use an external webcam on these boxes, and some of the files I have looked at suggest this. I do not currently have an external webcam that I can try this out with, but if someone else does, please inform me and I will update the information here.
External 3G/4G
It may also be possible to use an external USB SIM Card Modem to get data to work on these boxes (if ever needed). I do not currently have any such device that I can try this out with, but if someone else does, please inform me and I will update the information here.
Thanks: XDA, Freaktab, 4PDA

This section only contains the TWRP files. Other necessary files are in the next section.
How To Get Into LOADER Mode
Loader mode is needed in order to flash ROMs. If you simply connect your Android TV Box with the a USB cable to your PC and power it on, you will only get ADB mode, which will not work.
Plug in the USB cable to a PC and the Android TV Box.
Press and hold the reset button. (On the Z4L/Z4 it will be located on the bottom of the box. On some others it will be in the A/V port, so use a toothpick or paperclip).
Plug in the power adapter while still holding the reset button.
4 seconds should pass before it is in Loader mode.
Let go of the reset button.
DO NOT TRY TO PUT A THIN OBJECT INTO THE Z4L/Z4! There is no back (at least on the Z4L), which means you can go straight into the area of the PCB and possibly destroy something or disconnect the antenna cable.
How To Flash Firmwares/ROMs
You can use either the Android Tool or the Batch Tool to flash IMG files. I prefer Android Tool since it provides more options, but I will explain how to use both.
Open the program of choice.
Switch to the "Upgrade Firmware" tab if using Android Tool.
Click the "Firmware" button (or the 3 dots button for "FW Path:" if using Batch Tool).
Navigate to your "update.img", or the IMG file for your firmware/ROM.
Select the IMG file.
Click "Open".
Click "Upgrade".
The Batch Tool can only do firmware/ROM IMG files, but Android Tool will allow you to flash BIN or entire extracted ROM files.
How To Flash Extracted Firmwares/ROMs
The Android Tool can be used to flash extracted firmwares and ROMs. You will notice that the software comes with a "rockdev" folder filled with IMG and other files. I have come across at least one ROM that was extracted and needed Android Tool in order to be flashed. For the purposes of this tutorial, ROM is interchangeable with firmware.
Open the "rockdev" file of Android Tool.
Go to the "Image" folder.
Replace all the files in the "Image" folder with the extracted IMG files from the ROMs "Image" folder.
Go back up one folder (into "rockdev").
Replace all the IMG files with the extracted IMG files from the ROMs root folder.
If you have any extra files from the ROM that are present in the "rockdev" folder, replace those as well.
For at least the Z4L, be sure that you have the Loader BIN file that is version 2.40!
Open Android Tool.
Put your Android TV Box into Loader mode.
The first tab will show you all the IMG, TXT, and BIN files that you should have from your ROM in the "rockdev" folder. The only file you may not have, but should already be in the folder, is "baseparamer.img". The one that comes with Android Tool will suffice.
Ensure all the check boxes for each IMG, TXT, and BIN file is checked.
Click "Run".
Note: NEVER FLASH AN EXTRACTED ROM ALONG WITH A TWRP RECOVERY! The box will boot immediately into TWRP, making it impossible to ever get to the ROM itself!
Once the process has completed, which should take no more than a few minutes, your Android TV Box will no longer state that is in Loader mode, and will either state no device is connected or "Found One ADB Device". If you see this, or at least that you were successful on the message prompt of Android Tool, then you can go ahead and disconnect everything and boot your box!
How To Flash TWRP Recovery
You will need the Android Tool for this. Download either Abdul's TWRP, Generic TWRP, or Specific TWRP. I have tested and used Abdul's TWRP on the Z4L, and it works without issue.
Change the name of the TWRP IMG to "recovery.img".
Go to "rockdev>Image" of the Android Tool folder.
Replace "recovery.img" with the renamed TWRP IMG.
Open Android Tool.
Uncheck every box except "Recovery".
Put your Android TV Box into Loader mode.
Click "Run".
TWRP is now installed. I am unsure for the other TWRP IMG files, but the Abdul variant will require a mouse in order to be used because the remote is not supported.
How To Root
If your Android TV Box is not prerooted, then you will need to use SuperSU. Download SuperSU from here. If you want to try the latest version, you can find it here. Ensure that you already have TWRP installed.
Place the SuperSU ZIP on your internal or external storage.
Boot into TWRP.
Click on Install.
Add a zip.
Find your SuperSU ZIP file.
Select it.
Flash the ZIP file.
You should now be rooted and can check with an app from the Play Store to verify. I have not tested this as I do not need it, so if any steps are different, please let me know and I will change accordingly.
How To Flash Firmwares/ROMs with a SD Card
You will need the Upgrade Disk Tool and a micro/SD card that is 4GB or more. For the purposes of this tutorial, ROM is interchangeable with firmware, and SD card is interchangeable with micro SD card.
Open the Upgrade Disk Tool (SD Firmware Tool).
Select your SD card from the dropdown menu.
Click the "Firmware" button.
Find your ROM's IMG file.
Select it.
Click "Open".
Click "Create".
Once done, ensure your Android TV Box is turned off.
Insert the SD card into your Android TV Box.
Power on the Android TV Box.
The process will take some time, but a notification of a successful completion will appear when done.
Turn off the Android TV Box.
Remove the SD card.
Power on the Android TV Box.
The Android TV Box should now be "upgraded" to the firmware or ROM you used.
I want to remind people that every time you flash a firmware or ROM, it will take around 10 minutes for the Android TV Box's initial boot into the Android OS.
I may also put some more information here about how to open the compiled IMG files and play around with the system IMG file inside, if people want to know (and I have time).

The Rockchip drivers needed for these tools can be found in Batch Tool v1.8 as "DriverAssitant" [sic].
Android Tool
This is the probably the best tool for flashing and dumping firmware or ROM files:
Android Tool v2.35
Batch Tool
This is a great tool for flashing firmware or ROM files. It is the easiest to use:
Batch Tool v1.8
Batch Tool v1.7
Again, v1.8 has the drivers needed to make all the Rockchip tools function.
Factory Tool
This is a tool that should allow you to change things like the boot animation, add or delete APKs, and even make system clones. However, this does not work with the Z4L. The latest version gets close to completing its initialization process, but fails at the end, keeping all the options grayed out...
Factory Tool v3.4
Factory Tool v4.0
Factory Tool v4.4
Factory Tool v5.0
I have changed a couple of the versions to default to English (or as much English as afforded by the program without too much modification). The others were already in English.
Dump Tool
This is a tool that is essentially Android Tool. I believe that the version of Android Tool I have linked will perform the same functions, but this was one specifically made for dumping stock IMG files. I have used it unsuccessfully, as I can dump all the IMG files, but I am unable to make them work together. However, the "system.img" file may or may not work for modification purposes, but I have yet to check...
Dump Tool v2.3
IMG Mod Tool
This is a great and useful tool for those who want to modify firmwares or ROMs. It allows you to open firmware or ROM IMG files and recompile them. And despite its name, it does work for RK3368 Android TV Boxes.
RK3066 IMG Mod Tool
Upgrade Disk Tool
This allows for "upgrading" your Android TV Box with a different firmware or ROM.
SD Firmware Tool
If I have missed any tools that do something different, have extra functions, or simplify procedures; let me know and I will add them here.

Reserved..

Reserved...

Great consolidated info for Z4 / Z4L RK3368.
Different ROMs being developed for this beast, mostly Z4. IMO best, fastest and stablest is @yablrar mod v1.2 A multi window one is also there. I believe MM 6 is releasing soon.
On a side note:
An easier way to get into recovery/bootloader mode is to use an App like Titanium or other to reboot. No need to tinker around with reset/power buttons.

I have this android tv...should your firmware work in it?¿?
http://www.leotec.com/index.asp?acc...LEOTEC&familiaweb=TV&CodigoArticulo=LETVBOX02

Z4 Rockchip Bluetooth Issues
I have the Z4 Rockchip , I have tried 3 different firmwares and I can't bluetooth past 4 feet ? It has 4.0 , is there a way to upgrade it ?
Thanks

WAIKIKI728 said:
I have this android tv...should your firmware work in it?¿?
http://www.leotec.com/index.asp?acc...LEOTEC&familiaweb=TV&CodigoArticulo=LETVBOX02
Click to expand...
Click to collapse
It might work, yours looks like it does not have wireless AC, so there is a chance. Get a backup of your stock firmware, then try mine out. Be sure to check if your ports, WiFi, and Bluetooth work after flashing my firmware...
pimpurlid said:
I have the Z4 Rockchip , I have tried 3 different firmwares and I can't bluetooth past 4 feet ? It has 4.0 , is there a way to upgrade it ?
Thanks
Click to expand...
Click to collapse
The hardware will be near impossible to upgrade, and not worth your time. If you really want to have it work past 4 feet, you would need to buy a Bluetooth signal booster. However, if you are just using a mouse or keyboard, I would try getting a USB 2.4GHz device instead. Those seem to work much better.

Heatshiver said:
It might work, yours looks like it does not have wireless AC, so there is a chance. Get a backup of your stock firmware, then try mine out. Be sure to check if your ports, WiFi, and Bluetooth work after flashing my firmware...
The hardware will be near impossible to upgrade, and not worth your time. If you really want to have it work past 4 feet, you would need to buy a Bluetooth signal booster. However, if you are just using a mouse or keyboard, I would try getting a USB 2.4GHz device instead. Those seem to work much better.
Click to expand...
Click to collapse
Thank - You .

Have you tried getting a version of Linux installed on one of these Z4's?
Other other people have got the 64 bit arm version running on devices that use the same chip (RK3386 chip).

how get loader mode
Please help ... I can't make that my pc find the Z4 rk3368 in loader mode, just the ADB mode.. to install you costum ROM Z4L slim..
tank you..

Hi, been trying to install custom roms, with rockchip batch tool and android tool, i am in loader mode and with org cable but all i get is test device fail. I can update stock firmware with usb just can't get custom roms to work. Thanks for any help.

Z4L
Has anyone installed this rom, any feedback?
I have the Andoer Z4L and wanted to try this as I am experiencing some issues with audio via optical where it drops intermittently. Would any of the Z4 roms for RK3368 work on this device also?

Z4 ROM that should also work with the Z4L
d33pblu80 said:
Has anyone installed this rom, any feedback?
I have the Andoer Z4L and wanted to try this as I am experiencing some issues with audio via optical where it drops intermittently. Would any of the Z4 roms for RK3368 work on this device also?
Click to expand...
Click to collapse
My Z4 android TV (ATV) ROM should also work with the Z4L.
Just install my custom Z4 custom ROM available at freaktab. I'm a new user here at XDA so it's not allowed to me to post any external link. So just google for the name of my ROM. "[ROM] Z4 RK3368 - android TV (ATV) for Andoer Z4 - ENY EKB368 - Acemax AK838 - Tronfy X6"
Then just flash on top of that ROM the needed Z4L KRS files (resource & kernel) to activate the Z4L RTL8723bs WiFi chip (also described at my freaktab thread).
Good luck and much fun
-cOOLio-

In the end I gave up.
No one can tell me what is the most complete and working firmware.
All firmware always has something that does not work.
Now I still have the firmware 22.12.2015
It's not really a speed champion, but at least it works at all!

does anyone tell me how to get into recovery mode?
I would like to flash the supersu file, but I can not get into recovery

(Guided) LeTV LeEco Le 1 Pro (US Version) X800 TWRP Recovery, Root

The LeTV LeEco Le 1 Pro is an excellent phone that comes at a very low price. Some retailers are selling the phone for approx. £150. However, the phone does come with a few problems.
The phone comes bundled with an old YouTube app which refuses to update to the latest version. The phone has malware where apps are installed in the background and ads are served in the Chrome browser.
At the time of writing there was no official ROM available. Now a official ROM has been released. It can be found in this post. Installing the official ROM is the easiest way to fix the malware and app problems with the phone.
The TrustGo App from the Google Play store pointed out that the Ant Keyboard bundled app contained the malware. The YouTube problem can be fixed by uninstalling the bundled YouTube and installing the latest YouTube from the Google Play Store.
The phone had to be rooted to remove the YouTube and the malware app Ant Keyboard.
The following instructions will root the LeTV Le 1 Pro USA version only. However, rooting can brick your phone, so if you do go ahead it will be your responsiblity. Rooting also invalidates the warranty of the phone. You will also be able to unroot your phone at a later date and reinstate your warranty.
The following assumes that you are using Windows 10.
Rooting the LeTV Le 1 Pro USA Version
Install TWRP
TWRP will allow to root the phone. First it needs to be installed.
In order to install TWRP, you need to connect the phone to the PC
Lets prepare the PC before we connect it
Install Java JDK 8 using Chocolatey
Open an administrator command prompt
Type cmd in the search, right click Command Prompt and choose Run as administrator.
Copy and paste the following code into the administrative command prompt window to install chocolately
@powershell -NoProfile -ExecutionPolicy Bypass -Command "iex ((new-object net.webclient).DownloadString('https://chocolatey.org/install.ps1'))" && SET PATH=%PATH%;%ALLUSERSPROFILE%\chocolatey\bin
Install and configure JDK 8 by pasting the following code into the administrative command prompt window.choco install jdk8
Download, install and configure android studio using the defaults in the setup
Download Android Studio
Launch setup and accept the defaults
In the final screen select lanuch Android Studio and then finish
Choose the configure dropdown and then choose SDK manager
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In the SDK manager, check the Google USB Driver from the SDK Tools tab and choose OK
android sdk manager google usb driver
Close the administrative command prompt and then open a new administrative command prompt and type adb. You should see the adb command returning help. This means that adb driver is installed and ready to go.
Download the latest version of TWRP onto the PC using this link
Rename the downloaded file to recovery.img
Now it is time to prepare the phone before we connect it to our already prepared PC. If your phone does not boot into android then you can skip the whole of this #4 section and move on to #5 (TWRP) section below.
Go to settings and then about on your phone. Unlock developer options by touching the build number several times.
Android : Settings -> About
Go to settings, developer options and enable USB debugging
http://i0.wp.com/showtop.info/wp-content/uploads/2016/07/Screenshot_2016-07-11-14-22-04.jpg?resize=900%2C1600[IMG/]
Android enable USB debugging
In the notification bar click on touch for USB options and ensure that MTP is selected
[IMG]http://i1.wp.com/showtop.info/wp-content/uploads/2016/07/Screenshot_2016-07-11-15-16-45.jpg?resize=900%2C1600
Android USB Options
Connect the phone to the PC
In an administrative prompt check the phone is connected correctly by typing
adb devices
You should see a device under adb devices
Download SuperSU and use the file manager to put in the root directory of the phone
Lets flash TWRP into the phone. You should not lose any data, but if you have data on the phone you should make a backup just in case.
We need to boot into fastboot. On the PC, open an administrative command prompt and type
adb reboot bootloader
If your device does not boot into android, you can go into fastboot by switching off your phone, hold the down volume key and then press the power button.
Once in fastboot you should see a small picture of a penguin in the middle of the screen. To check that the phone is connected, in the administrative command prompt type
fastboot devices
You should see your device listed
In the administrative command prompt make sure you are in the directory of the recovery.img file and type the following
fastboot flash recovery recovery.img
Once the recovery is flashed type the following and hold the up volume key to restart in recovery
fastboot reboot
You should now be in TWRP. In TWRP there may be an option advanced or settings to install SuperSU. If the option is not there use install to install SuperSU (downloaded earlier) from the root of the phone storage.
Once installed you can reboot into android and following the instructions in the SuperSU app.
Once the installation is complete download the RootChecker app from the Google Play store and check if the device has been rooted.
Fixing the problems with YouTube and removing the malware
Install Easy Uninstaller, Stubborn Trojan Killer and Malwarebytes Anti-Virus from the Google Play Store.
Uninstall YouTube and Ant Keyboard. I uninstalled Cantonese Keyboard Language and Mii Browser as well as I was not using these. If you start getting errors, simply reboot your device.
Download and install the YouTube app from the Google Play Store.
Run the Stubborn Trojan Killer and remove any found trojans.
Run the Malwarebytes Anti-Virus and remove any found viruses. Run the privacy scanner and follow the recommendations.
Once you have successfully completed the above steps then your device should be malware free and completely usable.

Very nice job. Newbies friendly rooting guide. I think you must add another option in the poll : CM12.1 cooked by Betahydri. It's a fully functional ROM (only IR remote and DT2W don't work yet) for everyday use.

ctragas said:
Very nice job. Newbies friendly rooting guide. I think you must add another option in the poll : CM12.1 cooked by Betahydri. It's a fully functional ROM (only IR remote and DT2W don't work yet) for everyday use.
Click to expand...
Click to collapse
Thanks , for the feedback , you had a good idea but the system doesn't let me edit the post yet

Hello, can you please explain how I can confirm my phone is the international version. I bought it from AliExpress on China.
Please also provide the links to the TWRP and the Super SU. Thanks

Steveyknoxville said:
Hello, can you please explain how I can confirm my phone is the international version. I bought it from AliExpress on China.
Please also provide the links to the TWRP and the Super SU. Thanks
Click to expand...
Click to collapse
If you see CE0560 In the back of the phone, that means you have the international version.
For the TWRP, download Le1Pro_US_TWRP_3.0.2-0_CUOCO92.7z
For Root, download SuperSu-V2.76

Thank you very much. Mine does have that on the rear. This is my second le1 pro the first I hate bricked trying to root it and install recovery. So I have been scared to try this one without knowing which model it is. Do you know if there is a custom ROM or even better asop or CM room available for the international version.
Thanks for your help.
---------- Post added at 08:29 AM ---------- Previous post was at 08:28 AM ----------
Thank you very much. Mine does have that on the rear. This is my second le1 pro the first I hate bricked trying to root it and install recovery. So I have been scared to try this one without knowing which model it is. Do you know if there is a custom ROM or even better asop or CM room available for the international version.
Thanks for your help.

Steveyknoxville said:
Thank you very much. Mine does have that on the rear. This is my second le1 pro the first I hate bricked trying to root it and install recovery. So I have been scared to try this one without knowing which model it is. Do you know if there is a custom ROM or even better asop or CM room available for the international version.
Thanks for your help.
---------- Post added at 08:29 AM ---------- Previous post was at 08:28 AM ----------
Thank you very much. Mine does have that on the rear. This is my second le1 pro the first I hate bricked trying to root it and install recovery. So I have been scared to try this one without knowing which model it is. Do you know if there is a custom ROM or even better asop or CM room available for the international version.
Thanks for your help.
Click to expand...
Click to collapse
You can fix your first bricked phone from HERE.
To be honest, I have tried only two Roms
1- Clean Stock Rom, it's clean of all malwares and virus that came with the Chinese resellers Rom, its very stable, good battery life. only the double tape to wake up & color mod doesn't work, but easy to fix HERE, (IMPORTANT you need to have Stock recovery to flash the Clean Rom or to modify a file in the Zip archive of the Rom to work with TWRP).
2- CM12.1 ROM by BetaHydri, a great Rom very stable only Ir Blaster doesn't work for now. The best choice so far.
3- Other Roms CUOCO92 5.5.014S but I have never used it.

Thank you so much, worked a treat.
Now I have TWRP, CM and super su.
Thanks for all your efforts.

You should also try betahydri CM 12.1 I have it on my phone for about 3 months and runs great , no bugs , and the battery performance is the same.

Hi.
After brick I've rescued my letv le1 x800 Pro US and I flash Cuoco92 rom. I used this rom and it works very fine. XD XD

Maybe I am not looking well enough, but I did not see the TWRP link in your post.
Next to that I installed the Android Studio. But the SDK tabs in the SDK section are disabled with me. It also says that "Android SDK location should not contain whitespace, as this can cause problems with the NDK tool" as a warning. Could this be related to the fact that the tabs are disabled?

the only way to root this phone is by cuocco92 method, there is no other way

Z3 Compact from MarshMallow to Oreo step by step

Introduction
XDA members devil188, nailyk and Dobsgw created an Omni ROM for Xperia Z3 Compact. https://goo.gl/omqsSP
A great job.
It works, still has some bugs (20171213) but it is good enough to use as replacement for MM as it is now.
Many are afraid to root their device.
- Warranty void
- Device going black
- Not familiar with the steps to take.
Now is the moment to upgrade your device to Oreo
- Warranty is void anyway because your device is more than 2 years old. (test by clicking on the Support app on your device)
- Device going black ( that is your own risk and I take no responsibility whatever if you brick your device)
- This guide takes you by the hand (step by step)
- The rewards are manifold.
Your devices will be as new.
- Oreo has the latest security updates
- You can allways revert to stock MM
The biggest risk in my opinion is unlocking the device and losing DRM keys which affects low-light photo quality.
This risk can be overcome by making a backup of the TA partition and in case that does not work it can partly be repaired.
Let's start.
STEP 1 Backup
You don't want to lose important stuff, so you want to make a backup first.
Method 1
Use Xperia Companion and make a backup to your PC
Method 2
Use the Xperia Transfer Mobile app
Make a backup to the cloud or to SD card.
Method 3
Use Google.
A good explanation can be found here.
Method 4
Use adb
With adb you cannot restore on a non rooted device but we will go rooting the device anyway.
To read about adb look here.
When begin your backup take some extra safety precautions.
- Whatsapp -> settings -> chats -> backup, for a fresh backup
- Whatsapp extra security copy the Whatsapp directory from device memory to SD card or to PC
- Signal -> Import and Export and copy SignalPlaintectBackup.xml to SD card renaming it to SignalPlaintextBakup-201712XX.xml
- Copy DCIM (your pictures) from internal memory to SD card or to PC
- Google backup settings -> accounts & sync -> sync everything
- Copying can be done with TotalCommander
I suggest to try the different methods of backing up and don't forget to test restoring.
STEP 3 Install and use ADB
Because you will root your device and need to make a backup of the ta partition it is important that you are able to use adb.
I made a post on that subject here.
Most of you probably are on Windows 10.
In this ADB and Fastboot for dummies is explained how to install the drivers for Windows 10 (and 8)
When you read it carefully it will be no problem to set it up.
Warning!
Flashtool, which is mentioned in the setup for installing the drivers on Windows, can be polluted on some download sites with virus and/or malware.
Take care!
Drivers from Sony can be downloaded from here.
STEP 4 Root your Locked device
You can root your locked device by following the steps from this thread carefully.
I did'nt manage so I unlocked my device.
STEP 5 Backup DRM keys & TA partition.
As I said, I didn't manage to root the locked device.
It didn't restart into recovery and I couldn't install Superuser.
The original thread for TA backup can be found here.
STEP 6 Unlocking the device
Now that the problem of backing up the TA partition no longer exists the rest of the steps are rather easy.
Go to the Sony website to unlock your device and follow the instructions carefully.
The link on how to unlock is here.
STEP 7 Get the necessary files
You will need:
- TWRP to have recovery from here.
- The Oreo ROM from here.
- Gapps from OpenGapps. (choose ARM, 8.0 and stock)
- TA partition repair from here. Choose the Z3C version and download from Mediafire.
Download everything in one directory.
Websites where information can be found:
How to Root And Install Official TWRP Recovery For Sony Xperia Z3 Compact
Restore Lost Functionality on Your Unlocked Xperia Device
STEP 8 Putting it all together
We are almost finished.
- Connect your (running) device to your computer and copy OmniROM, SuperUser, OpenGapps and DRM Function Restore V3 to the Download directory on your device.
- Goto settings -> developer options -> switch USB debugging on (you have done this long before)
- Copy TWRPxxxx.img to your adb directory on your PC
- Find the adb directory (Minimal ADB and Fastboot), press the Shift key and right-click on the directory -> choose Open PowerShell window here.
- In the command window type <./adb devices> (without the ./ it won't work) (without the < and the> of course)
- On your Phone you have to permit adb debugging from your PC (you have done this long before)
- Device connected, positive answer on your screen
- issue the command <./adb reboot bootloader> to go into fastboot mode
- type <./fastboot devices> to see if all goes well
- type <./fastboot flash recovery twrp.img> or whatever the name of the twrp image is. twrp-3.0.2-1-z3c.img
- It takes just as sec and the screen shows its OK
- Boot up your phone by pushing vol-down and on/off together to go into recovery mode and TWRP will show.
- TWRP asks to change the system partition from read only -> Swipe to allow modification
- Choose WIPE -> Swipe to factory reset (patience)
- Go back twice (do NOT reboot) to goto the main menu and choose Install
- Goto the Download directory and choose
-> omni -> add more zips -> superuser -> add more zips -> open gapps -> add more zips -> DRM function restore
-> Swipe to confirm flash
- If you only install Omni and forget superuser and gapps you will end up with a non-system. DRM function restore is luxury.
- Wipe cache and Dalvik cache
- Automagic reboot will follow
- Unplug
- Be patient , the first boot of your Oreo loaded Z3 Compact will take a while.
Step 9 Hurray
You did it!
You ended up with a superb Z3 Compact!

@HvdW Please check your PMs
Also, there is some inaccuracies in your advice and statements in the above guide.

Thanks for your step-by-step guide. I think you don´t need the drm fix if you aren´t using a stock rom with unlocked bootloader.
Omni-ROM will bypass the loss of camera quality.
Since nougat (lineageOS, omni, carbon) developers found a way to have the camera working with the same picture quality as in stock rom.

SkyHigh76 said:
Thanks for your step-by-step guide. I think you don´t need the drm fix if you aren´t using a stock rom with unlocked bootloader.
Omni-ROM will bypass the loss of camera quality.
Since nougat (lineageOS, omni, carbon) developers found a way to have the camera working with the same picture quality as in stock rom.
Click to expand...
Click to collapse
Yes you do. Once you unlock the bootloader DRM functionality is gone. So on a stock ROM with unlocked bootlader you will need the DRM fix in order to fix the DRM functionality. If you use a custom kernel with the DRM fix already incorporated into it then you do not need to add it again as you are already using it. In either case, it is needed though...
@HvdW
I tidied up your OP. The missing step 2 is down to you. The original posts did not have a step 2, it went from step 1 to step 3.

Nice, I will try this early January, after Christmas

Thank You!
HvdW said:
Introduction
XDA members devil188, nailyk and Dobsgw created an Omni ROM for Xperia Z3 Compact. https://goo.gl/omqsSP
A great job.
It works, still has some bugs (20171213) but it is good enough to use as replacement for MM as it is now.
Many are afraid to root their device.
- Warranty void
- Device going black
- Not familiar with the steps to take.
Now is the moment to upgrade your device to Oreo
- Warranty is void anyway because your device is more than 2 years old. (test by clicking on the Support app on your device)
- Device going black ( that is your own risk and I take no responsibility whatever if you brick your device)
- This guide takes you by the hand (step by step)
- The rewards are manifold.
Your devices will be as new.
- Oreo has the latest security updates
- You can allways revert to stock MM
The biggest risk in my opinion is unlocking the device and losing DRM keys which affects low-light photo quality.
This risk can be overcome by making a backup of the TA partition and in case that does not work it can partly be repaired.
Let's start.
STEP 1 Backup
You don't want to lose important stuff, so you want to make a backup first.
Method 1
Use Xperia Companion and make a backup to your PC
Method 2
Use the Xperia Transfer Mobile app
Make a backup to the cloud or to SD card.
Method 3
Use Google.
A good explanation can be found here.
Method 4
Use adb
With adb you cannot restore on a non rooted device but we will go rooting the device anyway.
To read about adb look here.
When begin your backup take some extra safety precautions.
- Whatsapp -> settings -> chats -> backup, for a fresh backup
- Whatsapp extra security copy the Whatsapp directory from device memory to SD card or to PC
- Signal -> Import and Export and copy SignalPlaintectBackup.xml to SD card renaming it to SignalPlaintextBakup-201712XX.xml
- Copy DCIM (your pictures) from internal memory to SD card or to PC
- Google backup settings -> accounts & sync -> sync everything
- Copying can be done with TotalCommander
I suggest to try the different methods of backing up and don't forget to test restoring.
STEP 3 Install and use ADB
Because you will root your device and need to make a backup of the ta partition it is important that you are able to use adb.
I made a post on that subject here.
Most of you probably are on Windows 10.
In this ADB and Fastboot for dummies is explained how to install the drivers for Windows 10 (and 8)
When you read it carefully it will be no problem to set it up.
Warning!
Flashtool, which is mentioned in the setup for installing the drivers on Windows, can be polluted on some download sites with virus and/or malware.
Take care!
Drivers from Sony can be downloaded from here.
STEP 4 Root your Locked device
You can root your locked device by following the steps from this thread carefully.
I did'nt manage so I unlocked my device.
STEP 5 Backup DRM keys & TA partition.
As I said, I didn't manage to root the locked device.
It didn't restart into recovery and I couldn't install Superuser.
The original thread for TA backup can be found here.
STEP 6 Unlocking the device
Now that the problem of backing up the TA partition no longer exists the rest of the steps are rather easy.
Go to the Sony website to unlock your device and follow the instructions carefully.
The link on how to unlock is here.
STEP 7 Get the necessary files
You will need:
- TWRP to have recovery from here.
- The Oreo ROM from here.
- Gapps from OpenGapps. (choose ARM, 8.0 and stock)
- TA partition repair from here. Choose the Z3C version and download from Mediafire.
Download everything in one directory.
Websites where information can be found:
How to Root And Install Official TWRP Recovery For Sony Xperia Z3 Compact
Restore Lost Functionality on Your Unlocked Xperia Device
STEP 8 Putting it all together
We are almost finished.
- Connect your (running) device to your computer and copy OmniROM, SuperUser, OpenGapps and DRM Function Restore V3 to the Download directory on your device.
- Goto settings -> developer options -> switch USB debugging on (you have done this long before)
- Copy TWRPxxxx.img to your adb directory on your PC
- Find the adb directory (Minimal ADB and Fastboot), press the Shift key and right-click on the directory -> choose Open PowerShell window here.
- In the command window type <./adb devices> (without the ./ it won't work) (without the < and the> of course)
- On your Phone you have to permit adb debugging from your PC (you have done this long before)
- Device connected, positive answer on your screen
- issue the command <./adb reboot bootloader> to go into fastboot mode
- type <./fastboot devices> to see if all goes well
- type <./fastboot flash recovery twrp.img> or whatever the name of the twrp image is. twrp-3.0.2-1-z3c.img
- It takes just as sec and the screen shows its OK
- Boot up your phone by pushing vol-down and on/off together to go into recovery mode and TWRP will show.
- TWRP asks to change the system partition from read only -> Swipe to allow modification
- Choose WIPE -> Swipe to factory reset (patience)
- Go back twice (do NOT reboot) to goto the main menu and choose Install
- Goto the Download directory and choose
-> omni -> add more zips -> superuser -> add more zips -> open gapps -> add more zips -> DRM function restore
-> Swipe to confirm flash
- If you only install Omni and forget superuser and gapps you will end up with a non-system. DRM function restore is luxury.
- Wipe cache and Dalvik cache
- Automagic reboot will follow
- Unplug
- Be patient , the first boot of your Oreo loaded Z3 Compact will take a while.
Step 9 Hurray
You did it!
You ended up with a superb Z3 Compact!
Click to expand...
Click to collapse
Thank you! Excellent step by step baby guide. However <b><i>do</b></i> wish to point out to future people unlocking their bootloader that it is HIGHLY essential that you backup your TA before unlocking the bootloader.

What i did is: unlocked bootloader before i ever sow this post, installed custom stock based rom, red this post, backuped DRM, and DRM found and successfully backuped intact just like it was before unlocking on Z3Compact

OpenGapps 8.0 not working, you need 8.1.0 gapps.

Thanks for posting this guide. Is it ok to ask questions in this thread? Because I'm kind of stuck
I successfully completed every step until #6 "Unlocking the device". For some reason I can't get into fastboot mode anymore. The device shows a black screen, the LED is lighting up blue. Kernel version is 291. Phone has root access and SuperSU installed.
adb recognizes the device, fastboot does not - see attached image.
Any advice?

vinc9876 said:
Thanks for posting this guide. Is it ok to ask questions in this thread? Because I'm kind of stuck
I successfully completed every step until #6 "Unlocking the device". For some reason I can't get into fastboot mode anymore. The device shows a black screen, the LED is lighting up blue. Kernel version is 291. Phone has root access and SuperSU installed.
adb recognizes the device, fastboot does not - see attached image.
Any advice?
Click to expand...
Click to collapse
If u see blue led u are on fastboot.
Try adb fastboot comand after mast see same help comand, now try fastboot device.
Don't worry, take,it easy. GL
Maybe u are flashtool open, close flashtool.

yo7fb said:
Try adb fastboot comand after mast see same help comand.
Click to expand...
Click to collapse
I don't think I understand what you mean.
I think the bootloader is stuck somehow. Maybe something to do with the .291 ROM being incompatible with the bootloader? I'm pretty sure I should see the fastboot screen like so:
EDIT: Got it working!
Had to reinstall adb/fastboot drivers from the flashtool installation.

HvdW said:
Introduction
-> omni -> add more zips -> superuser -> add more zips -> open gapps -> add more zips -> DRM function restore
-> Swipe to confirm flash
- If you only install Omni and forget superuser and gapps you will end up with a non-system. DRM function restore is luxury.
- Wipe cache and Dalvik cache
- Automagic reboot will follow
- Unplug
- Be patient , the first boot of your Oreo loaded Z3 Compact will take a while.[/hide]
Step 9 Hurray
You did it!
You ended up with a superb Z3 Compact!
Click to expand...
Click to collapse
Thanks a lot for the detailed tutorial. I have a question because I stuck in the last steps. When says "superuser" refers to the superuser_238_291.zip file??? because I take that and I waited for more than 1 hour with following Oreo starting screen and never overcome that screen.

Hi guys! Thanks for the manual. I've followed all steps and I upgraded to 8.1.0
All is ok, but when I recive a call doesn't appear anything in screen. Only sound the ring, but I can't answer the call.

jhalvico said:
Thanks a lot for the detailed tutorial. I have a question because I stuck in the last steps. When says "superuser" refers to the superuser_238_291.zip file??? because I take that and I waited for more than 1 hour with following Oreo starting screen and never overcome that screen.
Click to expand...
Click to collapse
Hello.
I'm sadly in same situation as you are (or was). Did everything according to guide but it is 1.5 houre since it started booting.
Do any of you guys have tip what to do?
Btw: thanks for this guide
Edit:
So i managed to get it working by following steps from the Oreo rom page.

the battery on which version lives more?

probably google dialer?
uilino said:
Hi guys! Thanks for the manual. I've followed all steps and I upgraded to 8.1.0
All is ok, but when I recive a call doesn't appear anything in screen. Only sound the ring, but I can't answer the call.
Click to expand...
Click to collapse
Did you install google dialer? if so, go to
Settings--> Apps&notifications -->Advanced-->Default apps --> Phone app --> Select "Phone"

Error 7/6 when I try to install ZIP File via TWRP
Hey there, thank you very much for that easy install guide. Unfortunately I get stuck in my TWRP when I try to install the omnirom Zip. It showed error 7, then i edited the binary script file and it changed to error 6. Any kind of solutions here?

Hovenzius said:
Hey there, thank you very much for that easy install guide. Unfortunately I get stuck in my TWRP when I try to install the omnirom Zip. It showed error 7, then i edited the binary script file and it changed to error 6. Any kind of solutions here?
Click to expand...
Click to collapse
hi, i have got the same problem and i found this solution : https://forum.xda-developers.com/showthread.php?t=2522762

Restore with Xperia Companion
HvdW said:
STEP 1 Backup
You don't want to lose important stuff, so you want to make a backup first.
Method 1
Use Xperia Companion and make a backup to your PC
Click to expand...
Click to collapse
First thank you for your great post!
I try to restore my data after a successful upgrade and after having saved them with Xperia Companion but I can't succeed to make it detect my phone, so I can't use restore function... Do you know how can I achieve that? Is there some apk to install on the phone in order to make Xperia Companion recognize my phone and make restore function work?
Thanks!

Hi guys,
I have successfully followed this step-by-step:
How-to: root, keep and backup DRM keys, etc. [KitKat/Lollipops/Marshmallow/etc.]
and I also have unlocked the BL.
So, my Z3c has
- DualRecovery installed
(Z3C-lockeddualrecoveryX.Y.Z-RELEASE.installer.zip)
- superSU
- pre-rooted D5803 23.5.A.1.291
- backed-up TA
- unlocked BL
My question:
Do I still need to install Twrp or could I just boot into DualRecovery and flash CARBON-CR-6.1 + gaps from internal storage of phone?
Btw, if it isn't already blatantly obvious, I'm a total noob and without all the fine tutorials wouldn’t have a clue what I was doing.
Thanks for reading.

Nook Glowlight Plus 7.8 2019 (NGP7.8, BNRV700)

This one20092011201220132015201720192021Nook v1 Nook Simple TouchNook Simple Touch w/ GlowlightNook GlowlightNook Glowlight PlusNook Glowlight 3Nook Glowlight Plus (7.8 inch)Nook Glowlight 4
The other one
The 2019 Glowlight Plus shares the same name as the 2015 release. To avoid confusion, people began referring to it as the Glowlight 4, a name later used for the 2021 Nook release (surprisedpikachu.jpg). While the 2019 Nook is both confused with the 2015 and 2021 Nooks, it is less common than either. This makes it difficult to find compatible resources and tutorials.
This thread is for collecting the available resources for the 2019 Nook in one place, and eventually building a step-by-step guide for unlocking the potential of the device.
Why the BNRV700?
Three years after its release, it's currently the cheapest option for a reader with a screen size ideal for large format PDFs, such as textbooks. As of writing, the Nook Glowlight Plus (2019) can be found for half (or less) the price of other options with a similar display.
Unfortunately, the Nook ships with poor support for PDFs, sluggish hardware, severely outdated firmware (Android 4.4.2, released 2013) and lacks additional features like expandable storage. Some of these issues can be remedied, meaning the Nook could be a great option for many people, but only if it's safe and convenient to expand its functionality.
If you know of any useful resources or guides, please leave them in the comments below.
Note: This is an early work in progress. As of writing this, I don't have the device yet.

I'm reserving this space to put any resources, or document my experience with rooting or recovering the Nook Glowlight Plus 7.8 2019 (NGP7.8, BNRV700).
Resources
Technical
Hardware overview: Temblast​Backup and Recovery
TWRP: Github​Neo Noogie: Temblast, XDA-thread​Rooting
Magisk Root guide (Glowlight 4): Mobileread-thread​Caution: This guide is specifically for the Glowlight 4 (2021) rather than the Glowlight Plus 7.8 (2019) but it might be applicable.​RootGLP-3 script (Glowlight 3): XDA-thread​Caution: This resource is for the Glowlight 3 (2017) rather than the Glowlight Plus 7.8 (2019), however it has been reported to work.​RootGLP-3 script (2019 Glowlight Plus): XDA-thread​Note: This is a small modification of the Glowlight 3 (2017) root script for the 2019 Glowlight Plus, from wgznz (Chinese).​Firmware
Alternate ROM: XDA-thread​Software
Installing a launcher:​Installing apps:​Compatible readers and utilities:​Adding wallpapers:​Adding a software back button:​Physical button remapping:​Hardware
Expandable storage mod::​
High risk or incompatible resources
Mods
NGP Exposed module with fast refresh: Mobileread-thread​Supported: Nook Glowlight Plus (2015), Nook Glowlight 3​Notes: Due to the similarities between the NG3 and NGP7.8 (2019), someone might be able to get this to work, but it's untested.​

jun127 said:
I think more people would be willing to try it. But, between confusing and inconsistent naming making searches difficult (now even worse with the "Glowlight 4") and a lack of step-by-step guides, it's a minefield for the casual user to modify, and most aren't interested in the sub-standard Nook software.
Click to expand...
Click to collapse
I don't know whether you saw this and then dismissed it or just missed it: https://forum.xda-developers.com/t/gp-g3-gp7-8-twrp-alternative-firmware.4074347/
Seems like that might address most of the issues you have expressed.

nmyshkin said:
I don't know whether you saw this and then dismissed it or just missed it: https://forum.xda-developers.com/t/gp-g3-gp7-8-twrp-alternative-firmware.4074347/
Seems like that might address most of the issues you have expressed.
Click to expand...
Click to collapse
It looks like it could be a useful resource, but it seems like a lot of steps and cautions are ommitted. Although I've installed TWRP, rooted, and installed the fastink kernel (among other mods) on my old NST, I would hesitate (especially as a new user) to install alternate firmware without a clear procedure to first backup and revert everything to factory defaults or recover if something goes wrong.
Rough draft / work in progress (proceed at own risk)
Getting started
Download and install ADB
Using Android Studio
1: Download Android Studio
2: Scroll down and click on “SDK Tools Only”
3: Click on “ADB, Fastboot, and Platform Tools” and then click on the “Download” button.
4: After “adb_setup-x86.exe” is downloaded by the installer, run it and install adb inside the android SDK folder.
Using Minimal ADB and Fastboot
1: Download the installer or portable version (See: original XDA thread, latest version 1.4.3, 2018).
2: Install and run
Note: If you use the portable version, commands should be ran from the same directory. To open a console in the current folder on Windows, select the address bar, type cmd and hit enter.​
Enable USB debugging through developer options
1: Unplug the nook from the computer and turn the Nook on, register an account with Barnes and Noble and finish setting the device up.
2: Pull down the top menu
3: click "see all settings"
4: Press the down error on the bottom of the menu to go to the second page of settings
5: Press "about"
6: Tap the Nook logo until developer mode is enabled
7: Press "developer option settings"
8: Enable the "usb debugging" option
9: Connect the Nook to your computer. A popup will appear on your Nook asking to "turn on USB mode to safely move files..." click OK.
Note: This will cause your computer to download the appropriate drivers. After the drivers have been installed your Nook will show up in Windows Explorer and the Device Manager.​Note: When running commands over USB, sometimes it's necessary to temporarily disable mass transfer mode. To do this, go back to the developer options menu and select "disable mass storage".​Important: Remember to re-enable mass storage mode if you would like to drag-and-drop files onto your device using Windows file explorer later.​
Backup and restoration
The two most popular methods of creating and restoring backups are TWRP and Neo Noogie. If possible, it's best to have a backup from both. However, if you're not comfortable using the command line in Windows, you may choose to use TWRP only. Neo Noogie is a more powerful (complete) backup method, but it's easy to accidentally format your device or write a backup to the wrong Windows drive, either of which could be a nightmare.
TWRP is recovery software that is installed to the device, and provides a menu to backup and restore parts of the device to internal memory. You'll have to copy the recovery files from your device afterwards.
Neo Noogie can either be installed like TWRP or booted with fastboot. When booted into Neo Noogie, the entire flash memory is served to Windows and appears as a raw unformated drive. The internal storage can then be copied with special software. This has the advantage over TWRP in that it can be used to backup every aspect of your device, but you have to be very careful not to accidentally format the drive in Windows, as it could brick your device.
TWRP
Download TWRP
1: Download twrp_quill.img (may, 2020) from https://github.com/Ryogo-Z/nook_ntx_6sl_twrp/releases
2: Move twrp_generic to a folder (such as Documents\Nook)
Install TWRP
3: Power the NOOK BNRV700 off.
4: Hold the U button and then the power button until it starts into fastboot mode.
5: Connect the Nook to a Windows computer with USB, the drivers should be installed automatically.
6: Open the command prompt or Minimal ADB and Fastboot
7: Navigate to the folder you saved the TWRP image in (ex. starting from your user directory, enter "cd Documents\Nook").
8: Enter fastboot flash recovery twrp_generic.img to install TWRP
9: Enter adb reboot recovery (or interrupt startup 5 times) to enter TWRP recovery mode
Create backup with TWRP
Notice: (TWRP will not backup /storage/spsd as well as /data/media, which in practical terms means ...xyz...)
1: (I don't have a Nook anymore as my NST screen isn't working and haven't used TWRP in 10 years. I imagine it's something like boot into recovery/TWRP > Backup > check all the options > run)
2: Plug the Nook into the computer
3: Select USB mass transfer protocol
4: Open the Nook in file explorer and find wherever the recovery was saved to
5: Copy it to a safe place, like documents\nook.
Uninstall TWRP / reinstall stock recovery
The Nook's update file, 'update.zip' contains a copy of the stock recovery which can be reinstalled if you wish to return the Nook to factory defaults. However the stock recovery has fewer recovery features - so it is always safest to keep TWRP installed if you are tinkering with the device.
Rooting
Root Guide for the 2019 Glowlight Plus (using rootGLP)
1: Ensure you've enabled USB debugging tools from the developer options menu and saved a backup to a secure location
2: Connect the Nook to your computer. A popup will appear on your Nook asking to "turn on USB mode to safely move files..." click OK.
Note: This will cause your computer to download the appropriate drivers. After the drivers have been installed your Nook will show up in Windows Explorer and the Device Manager.​3: Disconnect the Nook and go back to the developer settings menu (see steps 2.1) and select "disable mass storage".
Note: This will prevent USB mode from interfering as we run the ADB script.​3: Download rootGLP.rar
Note: this is the same root script for the Glowlight 3, updated with the correct device name BGRV700. The original can be found in this XDA-thread. For a root guide for the Glowlight 3 using rootGLP, see this XDA-thread. The source is the wgznz forum (Chinese).​4: Extract rootGLP
Note: It's best to run the script from a location like C:\rootGLP\ or D:\rootGLP\.​5: Run the rootnook.cmd
Note: After the process is complete, you will see superSUfree appear on the screen. You will still need to install an alternate launcher.​
Installing apps
Installing a launcher and apps (doesn't require root)
If you haven't installed ADB, you can use the copy of adb.exe in the rootGLP-3\bin\ folder by following the instructions below. After installing a launcher, you should consider installing a file browser (such as ES file explorer) and a better web browser, so that you can download and install apps without connecting to your computer.
1. Make sure you have enabled USB debugging tools from the developer options menu and saved a backup to a secure location
2. Navigate to the rootGLP-3\bin\ folder.
3. Place the launcher .apk inside the bin folder with adb.exe.
4. Click the address bar in Windows Explorer and type "cmd" without quotes and hit enter. A windows CMD terminal will open at the current folder address.
5. type adb install launchername.apk (replace with the name of your .apk file)
Note: kk launcher and text launcher are known to work.​6. When you hit the U-shaped home button on your Nook, it will prompt you to select a launcher and ask if you would like to set it as the default. I recommend using "only once" at least until you can ensure you can always get back to the default launcher from whatever Android 4.4.2 compatible launcher you choose.
Installing KOreader and getting pageturn buttons working in KOreader (no root)
1. Download KOreader apk from https://koreader.rocks/
2. make sure your device is connected to adb and authorized with adb devices, if it t says "unauthorized", go to the developer menu (nook home > top right > all settings > page 2 > more > repeatedly tap logo) and tap "allow debugging".
3. install adb install koreader.apk. just hit tab to autocomplete the actual apk name.
4. Create a textfile "event_map.lua" in notepad and copy paste the following keymappings:
Code:
return {
[141] = "RPgBack",
[142] = "RPgFwd",
[140] = "RPgBack",
[139] = "RPgFwd",
}
5. use command adb push event_map.lua /sdcard/KOreader/settings/ to push the event map to the koreader settings.
6. If you had already installed and started KOreader before and just want to fix the keymapping, restart KOreader for the new settings to work (launcher > settings > apps > KOreader > force stop > home button > open KOreader > open book > test buttons > enjoy.

The stock recovery is not a big deal. It's in every update.zip
Just flash it with fastboot.
Why do you want it anyway when either TWRP or NeoNoogie is more powerful?

jun127 said:
It looks like it could be a useful resource, but it seems like a lot of steps and cautions are ommitted. Although I've installed TWRP, rooted, and installed the fastink kernel (among other mods) on my old NST, I would hesitate (especially as a new user) to install alternate firmware without a clear procedure to first backup and revert everything to factory defaults or recover if something goes wrong.
etc.
Click to expand...
Click to collapse
I am not the person to ask, but you are right that the first step is to be sure you can restore the device to stock. I'm one of those eccentrics who still loves and uses and continues to develop little improvements for the original NST/G, so all this fastboot stuff is pretty meaningless to me. I've flashed custom ROMs on Nook Tablets, but that's a totally different operation since back in the day Android was not locked up so tightly.
If you jut want a root guide (but it sounds like you want more than that): https://www.mobileread.com/forums/showpost.php?p=4202391&postcount=391

nmyshkin said:
I am not the person to ask, but you are right that the first step is to be sure you can restore the device to stock. I'm one of those eccentrics who still loves and uses and continues to develop little improvements for the original NST/G, so all this fastboot stuff is pretty meaningless to me. I've flashed custom ROMs on Nook Tablets, but that's a totally different operation since back in the day Android was not locked up so tightly.
If you jut want a root guide (but it sounds like you want more than that): https://www.mobileread.com/forums/showpost.php?p=4202391&postcount=391
Click to expand...
Click to collapse
I'd like to put together a simple guide, similar to what I wrote for the original NST about 10 years ago. I think the device needs a roadmap to outline what is currently possible in terms that are easy to follow. The device seems like it has a lot of potential, but it's just not very accessible at the moment.
I watched your video on running the CM on the NST, very interesting stuff and I'm glad to see some people are still keeping the device alive. I had used the original NST as a smartphone for a (short) while, even using it with Google phone and Whatsapp. It was surprisingly functional and, with the right optimizations, the battery could seemingly last forever with light use. Although it otherwise held up well, the rubber front panel and soft-touch back eventually degraded into a gooey mess. Removing the soft-touch coating on the back shell and replacing the rubber on the front with leather made it a more enjoyable reading experience for a while. Unfortunately, very poor app availability on Android 2.1 and the small, relatively low resolution display made it almost unusable for large format PDFs. Ultimately, the screen started failing and although it's still worth fixing, after 10 years it's overdue for an upgrade.
Renate said:
The stock recovery is not a big deal. It's in every update.zip
Just flash it with fastboot.
Why do you want it anyway when either TWRP or NeoNoogie is more powerful?
Click to expand...
Click to collapse
There's some peace of mind in knowing how to return things to exactly where you started. Even if unnecessary, there's always the possibility of some unforeseen issue and having a clear roadmap that you can follow to get back to the very beginning makes a difference in my mind.