Database Info

Simmtronics Xpad Freedom (MTK 6589) - 1 Stop Thread

Hello everyone, I was going through the threads and found out that there is no thread/device forum for Simmtronics Xpad Freedom.
It is a tablet running Android JB 4.2.2. It is a MTK based tablet (MTK6589).
{
"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"
}
NOTE
​Before starting, i would like to thank all the devs whose efforts made it possible to get the maximum potential of our device..
UPDATE: 1) Flashable Rom added (Flash using SP Flash Tools)
2) Stock Recovery Added.​
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
INDEX
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++​ 1. USB DRIVERS AND ADB INSTALLER
2. ROOTING THE TABLET
3. BACKING UP/ ROM DUMP
4. INSTALLING CWMR (ClockWorkMod Recovery)
5. FLASHING A ROM
6. FLASHABLE ROM DUMP
7. STOCK RECOVERY
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1) USB DRIVERS AND ANDROID ADB INSTALLER:-​
NOTE: BEFORE DOING ANYTHING PLEASE INSTALL THESE DRIVERS/ SOFTWARES FIRST AS THEY ARE NECESSARY FOR PERFORMING OPERATIONS.​
Tools Req:
1. USB VCOM Drivers for WINDOWS XP, WINDOWS 7 (http://www.4shared.com/rar/bHo5aN73/Usb_Vcom_Auto_Installer_v11236.html)
USB VCOM Drivers for WINDOWS 8/8.1: (http://www.patchworkoftips.com/how-to-install-mediatek-usb-vcom-driver-for-windows-88-1/3717/)
2. Adb Driver installer (https://drive.google.com/file/d/0B0MKgCbUM0itVVFWRC02Q0VBQnc/view?usp=sharing)
3. MTK DROID Tools (http://www.mediafire.com/download/6z9acf5um65cuj2/MtkDroidTools+v2.5.3.zip)
4. SP FLASH TOOLS (http://d-h.st/w6v or http://www.mediafire.com/download/aix6jxmcbxmmc2b/SP+Flash+Tool+3.1352.01+(5.1352.01).rar.html)
1.1) INSTALLING USB VCOM DRIVERS​
For Installing USB VCOM DRIVERS ON WINDOWS 8, 8.1 Click Here http://www.patchworkoftips.com/how-to-install-mediatek-usb-vcom-driver-for-windows-88-1/3717/
Installing USB VCOM Drivers on WINDOWS XP , WINDOWS 7 :
1. Connect your tab to the pc
2. Open Adb Driver installer on the pc. You will see your device in the list. Now click on Install button..
3. It will star installing the drivers and when it finishes its job a message will be displayed saying Adb driver installed.
4. Now extract USB VCOM drivers.. You will see these files in the folder
5. Now click on Install.bat. You will see a cmd prompt window..
6. Now click any button to close this window..
7. Now open adb 15 second installer.. you will see a security warning window.. Don’t worry just click run..
8. ADB 15 second installer window opens up asking for permission to install ADB and Fastboot.
9. Just type Y and press enter.You will see the following message.
10. It will ask you if you want to install device drivers.Type y and press enter.. It will display Device driver installation window.
11. Click Next.. It will start installing the drivers..When finished installing the drivers click on Finish.
________________________________________________________________________________________
2. ROOTING THE TABLET:-​
Update: You can also Root the device using Kingroot, Vroot
There are 2 ways in which you can root your device.. I will post both the methods..
::::::::::: METHOD 1 :::::::::::
Tools required:
1. Framaroot (http://forum.xda-developers.com/showthread.php?t=2130276)
Procedure:
1. Download latest Framaroot from the link given above
2. Make sure USB Debugging is enabled on your phone.If it is enabled proceed to STEP 8 , else follow these steps to enable USB Debugging first.
3. Go to Settings --> About tablet
4. Keep tapping on Build number till you get Developer option in settings
5. Go to Developer Option
6. Enable the developer option --> Click OK
7. Now click on USB Debugging --> Click OK
8. Go to security --> Click on Unknown sources --> Click OK to enable installation from unknown sources.
9. Now copy and paste the latest Framaroot to the desired location (Phone memory or Sdcard) by connecting it via usb and enabling USB mass storage.
10. Disconnect your phone and open File Manager.. Click on the internal storage if you have copied Framaroot to the internal storage else click on External Storage if copied to sdcard..
11. Find Framaroot in the desired location and click on it..You will see the following window on your tablet.
12. Click on Install.. Now open the app and click on any exploit.
[FONT=&quot]Congratulations!! Your device is now rooted[/FONT] :victory:​
::::::::::: METHOD 2 ::::::::::: ​
NOTE: MAKE SURE YOU HAVE INSTALLED USB DRIVERS AND ANDROID ADB FIRST OTHERWISE THIS METHOD WON’T WORK. IF YOU HAVEN’T INSTALLED ANY DRIVERS PLEASE REFER TO THE STARTING OF THE THREAD..​
Tools required:
1. MTKDroid Tools (http://www.mediafire.com/download/6z9acf5um65cuj2/MtkDroidTools+v2.5.3.zip)
2. Busybox (https://play.google.com/store/apps/details?id=stericson.busybox&hl=en)
Method:
1. Download MTKDroid Tools and extract it to the desired location.Click on MTKDroid Tools.exe and extract it to desired location.
2. Download Busybox on the tab via Google Playstore
3. Connect your tablet via USB and and make sure USB debugging is enabled.
4. Open MTKDroid Tools..The tool will recognize your device..If the color indicator in the bottom left corner is green, you already have root shell, and can go on to the next step, if it is yellow, click on the root button at the bottom, and wait for the progress bar, if the indicator stays yellow, or you get an error message, this probably means you do not have Busybox installed, you can install it from the Google play store. When the indicator turns to green you have root shell.
_____________________________________________________________________________________________________
3) BACKING UP ROM AND MAKING IT FLASHABLE VIA SPFLASH TOOLS:-​
Note: Backup will only work if you have root on your device
Tools required:
1.MTKDroid Tools
Method:
1. Download and open MTKDroid Tools.
2. Next click on the tab 'root,backup,recovery' and click on "backup"
[FONT=&quot]3. The process will now start. It may take at least 30 minutes to 1 hour depending on how many apps are installed on your phone. During the backup process you may see a pop-up asking if you want to make a compressed file for the backup. You can choose not to create the compressed file by clicking on “No”. It will same time but I recommend clicking on “Yes”.
[/FONT]
4.Once the backup has been completed check out the folder that contains your MTK Droid Tools application and you will see a folder named “backups”. The folder will contain all the images that you can use to flash using SP Flash tool and a zip file which is just a compressed files of the backup created by the droid tool. You can also see on your phone that there is a new folder named clockwordmod inside that there will also be a images that you can use to backup your rom using Clockworkmod (CWM).
5. Now to make this backup flashable through Sp Flash tools click on root,backup,recovery tab and click on To prepare blocks for Flash Tool
6. A new window will appear asking for .md5 file...For this navigate to MTKdroid Tools folder and then backups folder...Open the backup you have created earlier and select the files.md5 and click open.
7. Wait for the MTK Droid tools to copy the files for Sp Flash tools.. When the tool completes its job there will be a message "copying is complete"... Now you have a flashable backup of the rom...
______________________________________________________________________________________________________
4) Installing CWMR (ClockWorkMod Recovery) Using MTKdroid Tools:
​
NOTE: Your phone must be rooted before installing ClockWorkMod Recovery (CWMR)​
Tools required:
1. MTKDroid Tools
Method:
1. Open MTKdroid Tools and click on tab [FONT=&quot]'root,backup,recovery' and select 'to use boot from phone'
2. Then click on 'recovery and boot' and shortly after a dialogue box will appear asking if you want to 'make cwm recovery automatically' click yes [/FONT]
3. The tool will then create the recovery and another dialogue box will appear asking to 'install created recovery to phone', click yes and finally the tool will ask to reboot into recovery mode, click yes and the device will reboot into CWM recovery so you can check the installation was successful.
_____________________________________________________________________________________________________
5) FLASHING A ROM:-
​
NOTE : PLEASE DON’T FLASH ROMS WHICH ARE NOT COMPATIBLE WITH YOUR DEVICE AS IT CAN BRICK YOUR DEVICE. ​
​
Tools required:
1. SP Flash Tools (http://d-h.st/w6v or http://www.mediafire.com/download/aix6jxmcbxmmc2b/SP+Flash+Tool+3.1352.01+(5.1352.01).rar.html)
Method:
1. Download and open SP Flash tools.
2. Then click Scatter-loading button to load the correct scatter file. Select The scatter file which you have made using SpFlash Tools..If you are unable to find the scatter file for your tab head over to MTKdroid Tools folder --> backups.. Click on the backup folder (Folder name will be like Freedom_...._backup_.... Instead of dots there will be date/year)
3. Now click on “ !Files_to_FlashTool ” folder.. There will be a text file named as “ MT6589_Android_scatter_emmc.txt ” click on that text file and click open..
4. Now switch off your tab and disconnect it from your pc.
5. Press F9 (or hit Download button) and then connect your phone/tab into the computer via USB data cable and switch on the tab..After connecting the tab press VOL DOWN and VOL UP key.. The process will start and a red progress bar will appear.
6. After the red progress bar is complete, there will appear a purple progress bar.
7. After purple, yellow bar will appear. When the yellow bar is complete, you'll get a popup with a green circle , which means that the flashing process has been successful.
8. You can now safely disconnect your phone and turn it on.​
__________________________________________________________________________________________
6) Flashable Rom Dump/Backup
NOTE: I will not take any responsibility if something goes wrong while flashing this ROM.... I have personally flashed it on my device and it works...PLEASE BEFORE FLASHING READ "FLASHING THE ROM" SECTION OF THIS THREAD or refer to the original SP flash tools guide.. ​_______________________________________________________________________
THIS ROM IS PRE-ROOTED AND CWM FLASHED...Here is the
LINK: https://drive.google.com/file/d/0B7ujzTEVERI_X1JOemxkZUt2X00/view?usp=sharing
______________________________________________________________
Method:
1) Please see the Flashing a ROM section of this thread and make sure you have adb and other drivers installed..​ ___________________________________________________________________
7) Stock Recovery
​Here is the stock recovery of the device (credit goes to my friend @Ips666) :
https://drive.google.com/file/d/0B7ujzTEVERI_ZElnY093bkxKaFU/view?usp=sharing
________________________________________________________________________________
​

[Tutorial] QHSUSB_DLOAD Hardbrick Fix for I9505

Hello.I had my phone updated from 4.2 to 4.3 a few days ago and after updating itself in recovery,it simply died.No charging,no battery pull reset,just plain dead.I connected it to my laptop and it recognised it as QHSUSB_DLOAD.After googling around i found that only a JTAG will save it.Well,that ain´t true.I will give you a tutorial that will fix your phone in a few minutes.
First of all,i did it on Windows 8.1 x64.
Prerequisites :
QDLoader HS USB Driver : x64 driver or x32 driver
I9505 Pit file : Pit file download
Boot repair tool : I9505 Boot repair tool
Needed files to enter download mode to flash a stock rom : Files for Download Mode
Stock ROM to flash.I used this one but IT IS FOR THE LTE VERSION. Please download the stock rom for the Non - LTE version if you have it.
And lastly,Odin : Download here
Step 1.
Make sure that your device is connected and in Device Manager , it show as QHSUSB_DLOAD .If it does,disconnect it from your computer.
Before installing the drivers,we need to disable driver signature enforcement.
First,press WinKey + C and choose Settings
{
"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"
}
or if you prefer the modern one in Windows 8.1 or Windows 10,choose Change PC Settings
Choose Update & recovery
Click Recovery
Then,at Advanced Startup,click Restart now.
Your PC will restart.
Click Troubleshoot
Advanced Options
Startup Settings
Once entered here,it will ask for us to restart.Click Restart
When at the list,press F7 to disable Driver signature enforcement and boot.
Step 2.
Install the 64 bit or 32 bit driver depending on your OS WITH YOUR DEVICE DISCONNECTED.
Now plug your device to your computer via USB and it should pop up in Device Manager as Qualcomm HS-USB QDLoader 9008
Next,go to Control Panel,choose Folder Options and check Show hidden files.
Make a new folder on your desktop and put the galaxy_S4_9505 boot repair QHUSB in that folder and nothing else.
Now extract the needed files for Download Mode in another folder and leave it open and the folder you have galaxy_S4_9505 boot repair QHUSB open aswell.
Open galaxy_S4_9505 boot repair QHUSB and do not click Recover Device until you read the next step.
Step 3.
This is the most important step because we will flash the stock boot files for our device.
With galaxy_S4_9505 boot repair QHUSB open and the two folders above open, select all the files in the needed files for Download Mode folder and be ready because when you click Recover device,you will need to drag those files in the folder where galaxy_S4_9505 boot repair QHUSB is and you have to be very fast when doing it.
Click Recover Device and drag the files in the folder mentioned above and click overwrite very fast.This should be done in 3 seconds max. and if it won´t work,repeat the last step until you do it right.
Your phone should now boot in Download Mode.
Step 4.
Download Odin and click on AP and select the .tar file and wait a few minutes.
Click on Options and check Auto Reboot , Re-Partition and F. Reset Time. Make sure that these are the only checked options.
Now go to Pit tab and select the downloaded pit file.
Click start and wait for it to finish.
That is it.
Final note :
If your device is restarting and it does not boots in Download mode and shows up that the battery is charging,disconnect it and pull the baterry and the press Vol. down , Home button and Power to enter Download mode.If you do not flash a stock ROM with Odin,after your first restart,it will become hardbricked again.
Don´t forget to hit that thanks button if it helped you.
Goodluck.

i can dbrick s4mini gt-i9195 please help

It will work with my Galaxy S4 Active (SHV-E470s)?

Can you force the QHSUSB_DLOAD
Help !!!
After trying the procedure, I did not timely drag the files !!! Now it turns green all the green screen, but when I connect it to the pc no holes detected no door !!! Can you force the QHSUSB_DLOAD or Qualcomm HS-USB QDLoader 9008 ???? Sorry my bad english !!!
It is also possible for s4 mini i9195 ????

Thank you so much ,it worked for me on Windows 7. Galaxy s4 I9505.

thank you soooooooooooooooooooooooo much.!?

video please please

After trying this method . Don't u suffer from any display problem ? I tried this and it worked for me but i have now display problem . it's a little yellow and it appears always download mode .

Can I backup my phone when in download mode?

i got status 29 error: system could not write the files to specified device please help

Can this be made for a i9195 model???

kent8hd said:
Hello.I had my phone updated from 4.2 to 4.3 a few days ago and after updating itself in recovery,it simply died.No charging,no battery pull reset,just plain dead.I connected it to my laptop and it recognised it as QHSUSB_DLOAD.After googling around i found that only a JTAG will save it.Well,that ain´t true.I will give you a tutorial that will fix your phone in a few minutes.
First of all,i did it on Windows 8.1 x64.
Prerequisites :
QDLoader HS USB Driver : x64 driver or x32 driver
I9505 Pit file : Pit file download
Boot repair tool : I9505 Boot repair tool
Needed files to enter download mode to flash a stock rom : Files for Download Mode
Stock ROM to flash.I used this one but IT IS FOR THE LTE VERSION. Please download the stock rom for the Non - LTE version if you have it.
And lastly,Odin : Download here
Step 1.
Make sure that your device is connected and in Device Manager , it show as QHSUSB_DLOAD .If it does,disconnect it from your computer.
Before installing the drivers,we need to disable driver signature enforcement.
First,press WinKey + C and choose Settings
or if you prefer the modern one in Windows 8.1 or Windows 10,choose Change PC Settings
Choose Update & recovery
Click Recovery
Then,at Advanced Startup,click Restart now.
Your PC will restart.
Click Troubleshoot
Advanced Options
Startup Settings
Once entered here,it will ask for us to restart.Click Restart
When at the list,press F7 to disable Driver signature enforcement and boot.
Step 2.
Install the 64 bit or 32 bit driver depending on your OS WITH YOUR DEVICE DISCONNECTED.
Now plug your device to your computer via USB and it should pop up in Device Manager as Qualcomm HS-USB QDLoader 9008
Next,go to Control Panel,choose Folder Options and check Show hidden files.
Make a new folder on your desktop and put the galaxy_S4_9505 boot repair QHUSB in that folder and nothing else.
Now extract the needed files for Download Mode in another folder and leave it open and the folder you have galaxy_S4_9505 boot repair QHUSB open aswell.
Open galaxy_S4_9505 boot repair QHUSB and do not click Recover Device until you read the next step.
Step 3.
This is the most important step because we will flash the stock boot files for our device.
With galaxy_S4_9505 boot repair QHUSB open and the two folders above open, select all the files in the needed files for Download Mode folder and be ready because when you click Recover device,you will need to drag those files in the folder where galaxy_S4_9505 boot repair QHUSB is and you have to be very fast when doing it.
Click Recover Device and drag the files in the folder mentioned above and click overwrite very fast.This should be done in 3 seconds max. and if it won´t work,repeat the last step until you do it right.
Your phone should now boot in Download Mode.
Step 4.
Download Odin and click on AP and select the .tar file and wait a few minutes.
Click on Options and check Auto Reboot , Re-Partition and F. Reset Time. Make sure that these are the only checked options.
Now go to Pit tab and select the downloaded pit file.
Click start and wait for it to finish.
That is it.
Final note :
If your device is restarting and it does not boots in Download mode and shows up that the battery is charging,disconnect it and pull the baterry and the press Vol. down , Home button and Power to enter Download mode.If you do not flash a stock ROM with Odin,after your first restart,it will become hardbricked again.
Don´t forget to hit that thanks button if it helped you.
Goodluck.
Click to expand...
Click to collapse
Plz help me i am using this tutorial to fix my p5100 device but it shows permission denied . Other then samsung note 4 repair tool , I got appropriate things for my device. Plz help

Thank you a lot! It worked!
It took me a bit of time, this is my extra info for others:
- When doing the step 3, a command window with scrolling text will appear with 2 lines. You must do the copy paste thing BEFORE the text starts rolling as that indicates it started using those files. If no window with text opens, try again
- With odin I had 2 problems: One, that it was failing to do the copying, the reason was that I was using a wrong ROM. Second was that a ROM was written, but it was the incorrect one so I had to start again from step 0.
So try a different ROM.
I read the cable may be a problem too, but it wasn't in my case.
In between retries and after succeeding, removing the usb cable AND the battery may help.

CUBOT X19 [ TWRP 3.3.1 + Root ]

{
"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"
}
TWRP 3.3.1 + Root
This topic is the result of work mehanik6 (4PDA) my greetings to him
Tested on Android 9
1 - Remember that everything you do, you do at your own risk
2 - to install TWRP, we will have to unlock the bootloader, all data will be erased, Your device becomes out of warranty
3 - the you need to be installed adb driver For connecting your device to a computer (15 Second ADB Installer v1.5.3.zip)
How to install Best Android ADB Driver on your computer
How to Install Google USB Driver for Windows | ADB and FastBoot
installation
- download the archive delete_verity_key.zip without unpacking put on the sdcard (Attached file) delete_verity_key.zip (130.56 KB)
- download file Fix_vendor.zip without unpacking on the sdcard (Attached file) Fix_vendor.zip (347.64 KB)
- download file Magisk-v20.1.zip without unpacking on the sdcard (Attached file) Magisk-v20.1.zip (5.22 MB)
- download file adb.zip. unzip to your computer desktop adb.zip (22.02 MB)
- Enable developer options in Android
GO to Settings > Swipe down and tap on About Phone Keep tapping on the build number for 7 times
-Enable the USB debugging option
GO to Settings >System -> Developer options on your Android device and enable the USB debugging option.
-Enable “OEM Unlocking”
GO to Settings > Developer options on your Android device and enable the OEM Unlocking option.
when you plug the device into an PC, it will prompt you to allow USB debugging (as seen in the screenshot below).
- allow unlocking of the bootloader
- Decompress a folder adb.zip
- Open a command prompt inside a folder adb. right mouse button l menu, select to open a command window
- copy and paste command [adb devices] (Check Device by Sending below Command)
Example of making sure to connect to the phone
1
Code:
adb devices
2
Code:
adb reboot-bootloader
3
Code:
fastboot devices
If the device does not recognize the phone, it is on "fastboot" android adb interface
Installing [Google ADB Drivers] To Windows 7/8/8.1/10/XP/Vista
- download file Google ADB Drivers.zip
- unlock the bootloader
4
Code:
fastboot flashing unlock
- on the screen text appears, press the Volume + button (all data will be erased)
Attention
The following files(fileFix_vendor.zip+delete_verity_key.zip+Magisk-v20.1.zip) must be placed in an external card, because all phone data will be deleted
Then long press buttons (Power) to turn off the phone
- The bootloader is unlocked. You should see the Orange State (text).
Then turn ON the phone
one more time
- Enable developer options in Android
GO to Settings > Swipe down and tap on About Phone Keep tapping on the build number for 7 times
-Enable the USB debugging option
GO to Settings >System -> Developer options on your Android device and enable the USB debugging option.
when you plug the device into an PC, it will prompt you to allow USB debugging (as seen in the screenshot below).
- Open a command prompt inside a folder adb. right mouse button l menu, select to open a command window
1
Code:
adb devices
2
Code:
adb reboot-bootloader
3
Code:
fastboot devices
- Sew vbmeta.img (the error does not pay attention)
4
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
5
Code:
fastboot flash recovery recovery.img
-After completing:
*Long press buttons (Power) to turn off the phone And quickly Boot into TWRP (buttons Power + Volume Up )
By pressing the volume up selects: recovery mode
and pressing the( volume down) to start TWRP
Changes will not be saved language and settings in (TWRP) Only after all stages have been completed
- Back to the section mount
And put a tick next to all sections on which are placed
- go to the section wipe
- click Format the Data
- In the terminal, Type "yes" and confirm (format action) by click the check mark in the lower right corner
- then you need to reboot again in TWRP
Boot into twrp buttons (Power + Volume Up )
By pressing the volume up selects: recovery mode
and pressing the( volume down) to start TWRP​one more time​
- Go to the section mount
And put a tick next to all sections on which are placed
Back to install
- Flash archive delete_verity_key.zip
- Flash archive Fix_vendor.zip
- Flash archive Magisk-v20.1.zip (Data again to not encrypt)
- Restart the phone
Like everything, use
NEXT
[GUIDE] CUBOT X19​

I just rooted my phone and this guide was very helpful.
- After formatting your phone, boot into recovery through TWRP as my phone keeps bringing up the "no command" error screen if I use "Vol Up + Power"
- When that happens, hold power button for 10 secs, your phone will either turn off or reboot, flash TWRP again and continue.

Successfully Installed TWRP 3.3.1 with SP tool what is did After selecting scatter file from stock firmware i replaced the stock recovery and edit the partition size in the scatter fie for recovery and changed the default path from sp tool default was Recovery-verified i switch it to the Recovery.img that i replaced it with.

Having issues: At the top of the screen its written in red letters as overlay: "TEE key not write Google key not write"
I already applied the "fix Orange state" fix.
Any ideas?

Actually I am using a CubotX19 S and finally I went back to stock rom. That fixed the issue.
However, when I flashed Stockrom I noticed at loading of MT6763 scatterfile, that there are 2 sections having "tee" in their names (see screenshot).
Maybe it would be enough to just flash one or both of those two sections.
I did not do any further research, but maybe this hint os of help for others .
BTW: my screenshot says "Download only" in the Droplist. Actually I flashed using "Firmware Upgrade"
best regards,
bul

where do i get the vbmeta file from?

brezzz said:
where do i get the vbmeta file from?
Click to expand...
Click to collapse
recovery.img + vbmeta.img in folder adb.zip above
or https://www.mediafire.com/file/owuv9h2444w264y/adb.zip/file

flashing vbmeta failed "this partition doesnt exist"

kusti420 said:
flashing vbmeta failed "this partition doesnt exist"
Click to expand...
Click to collapse
Try the following at your own risk ​
You might have a problem partitioning the phone memory
format your phone
flash your phone
select : format all + download
the latest firmware for CUBOT X19 upgrade 2020-04-21
format your phone
Then try again according to the instructions in the next topic
TWRP 3.3.1 + Root CUBOT X19

karim.a said:
Try the following at your own risk ​
You might have a problem partitioning the phone memory
format your phone
flash your phone
select : format all + download
View attachment 5188523
the latest firmware for CUBOT X19 upgrade 2020-04-21
format your phone
Then try again according to the instructions in the next topic
TWRP 3.3.1 + Root CUBOT X19
Click to expand...
Click to collapse
hmm, i tried it just like it said, still cant see a vbmeta partition

karim.a said:
Try the following at your own risk ​
You might have a problem partitioning the phone memory
format your phone
flash your phone
select : format all + download
View attachment 5188523
the latest firmware for CUBOT X19 upgrade 2020-04-21
format your phone
Then try again according to the instructions in the next topic
TWRP 3.3.1 + Root CUBOT X19
Click to expand...
Click to collapse
also i saw someone say that this vbmeta is android 9 thing, but cubot x19 came with android 8.1, should it even have the vbmeta partition? how could i create that partition?

My friend kusti420, follow the instructions below, including upgrading the phone to Android 9 . If your phone has a android 8
Try the following at your own risk​
You might have a problem partitioning the phone memory
format your phone
flash your phone
select : format all + download
the latest firmware for CUBOT X19 upgrade 2020-04-21
format your phone
Then try again according to the instructions in the next topic
TWRP 3.3.1 + Root CUBOT X19

For one reason or another, my serial number of my phone is 0123456789ABCDEF and I can't flash the recovery, neither boot from it, nor flash the modified firmware with it.

I tried to flash vbmeta, but it did not do anything.

chartek1 said:
For one reason or another, my serial number of my phone is 0123456789ABCDEF and I can't flash the recovery, neither boot from it, nor flash the modified firmware with it.
Click to expand...
Click to collapse
How to find phones serial number or IMEI number​
Step 1. Open the Phone app.
Step 2. Dial *#06# on the keypad.
Step 3. Details about your devices IMEI and serial number will automatically appear on the screen.

chartek1 said:
I tried to flash vbmeta, but it did not do anything.
Click to expand...
Click to collapse
format your phone
flash your phone if model number CUBOT X19
the latest firmware for CUBOT X19 upgrade 2020-04-21
select : format all + download
format your phone
Then try again according to the instructions in the next topic
TWRP 3.3.1 + Root CUBOT X19

karim.a said:
format your phone
flash your phone if model number CUBOT X19
the latest firmware for CUBOT X19 upgrade 2020-04-21
select : format all + download
format your phone
Then try again according to the instructions in the next topic
TWRP 3.3.1 + Root CUBOT X19
Click to expand...
Click to collapse
Trash, description on two pages, but no link to TWRP, much to do, nothing to get from./translate/

user132 said:
Successfully Installed TWRP 3.3.1 with SP tool what is did After selecting scatter file from stock firmware i replaced the stock recovery and edit the partition size in the scatter fie for recovery and changed the default path from sp tool default was Recovery-verified i switch it to the Recovery.img that i replaced it with.
Click to expand...
Click to collapse
How do i adjust the file?

karim.a said:
format your phone
flash your phone if model number CUBOT X19
the latest firmware for CUBOT X19 upgrade 2020-04-21
select : format all + download
format your phone
Then try again according to the instructions in the next topic
TWRP 3.3.1 + Root CUBOT X19
Click to expand...
Click to collapse
Should I tick the preloader? I have heared that it might brick the device.

chartek1 said:
Should I tick the preloader? I have heared that it might brick the device.
Click to expand...
Click to collapse
I tick the preloader? NO​If the current Firmware (Stock ROM) for the phone is android 9​​​Instructions to Install​Charge the device battery up to 50%​
Make sure you follow and download all the required files and flash tools on your PC.
Open the flash tool exe file to open the SP Flash Tool User Interface
Tap on the Download option and load both the download agent and the scatter text file in the scatter-loading section.
Once you load the file, click the Download button
To start the upgrade process of stock ROM on your Cubot X19, you need to turn off your device and hold the Volume Down and Volume Up key together and Connect your Phone to PC/Laptop using USB Cable (Keep the Volume Down and Volume Up button until your computer detects the phone.)
When the phone connects, your device will start upgrading the stock firmware
Wait for a few minutes, If you see a green button on your flash tool which means the upgrading process has been completed.
That’s it! You can reboot your Cubot X19

Question New P11 stuck on Fast Boot after update

Hi,
I used Rescue and Smart Assistant to install the latest firmware on my new P11, which finished successfully, however,now it is stuck at fast boot and when I choose to enter Recovery Mode it starts again in Fast Boot.
I tried also flashing using qfil, it also finished successfully, but still stucked in fast boot.

I managed to make it working after updating it using Smart Assistant, I guest that I entered the two-digit hardware code wrong.

Hi! I am having this kind of problem too for the past week after i bought it tried to update it. Can you elaborate how you manage to fix it because even if i use QFIL, it's not letting me to flash the hardware. Hoping for your response and thank you!

You can try this:
1. Don't connect your tablet with PC.
2. Press Power button + Volumn (+) + Volumn (-) for seconds for get out flashboot mode.
3. Flash ROM version 210520 with Qfil.
This is work for my P11 CN version.

Me too. Please help

mklevi said:
You can try this:
1. Don't connect your tablet with PC.
2. Press Power button + Volumn (+) + Volumn (-) for seconds for get out flashboot mode.
3. Flash ROM version 210520 with Qfil.
This is work for my P11 CN version.
Click to expand...
Click to collapse
can you elaborate what settings on qfil , i have lenovo p11 4/64gb version

famicom9x said:
can you elaborate what settings on qfil , i have lenovo p11 4/64gb version
Click to expand...
Click to collapse
A. Qfil-Configuration-FireHoseConfiguration:
1. device type: ufs
2. Reset After Download: check
turn it off, disconnect to PC, open Qfil, press down the "volume +" buttom (do not release) and connect to pc (release till Qfil shows "Qualcomm HS-USB QDLoader 9008(comx)").
B. the main window:
load content: the contents.xml file
build type: meta
then press download content and wait till it boots.

asukav said:
A. Qfil-Configuration-FireHoseConfiguration:
1. device type: ufs
2. Reset After Download: check
turn it off, disconnect to PC, open Qfil, press down the "volume +" buttom (do not release) and connect to pc (release till Qfil shows "Qualcomm HS-USB QDLoader 9008(comx)").
B. the main window:
load content: the contents.xml file
build type: meta
then press download content and wait till it boots.
Click to expand...
Click to collapse
thank, there are a setting calledd "
Availible Meta Build Storage Types"
what must i choose? emmc or ufs?

Download with the Smart Assistant Tool from Lenovo latest firmware version TB_J606F_S320029_210923_ROW.
First Start Qfil.
The Qfil file is where the new firmware by Rescue and Smart Assistant is stored.
For me it was in the folder c:/ProgramData/RSA/Download/RomFiles/ToolFiles/Qfil
1: The tablet must not be connected to the computer and must be off.
2: Now start Qfil, at the top of the screen is now "No Port Available" start now the tablet by holding down the Volume + button and at the same time connecting the USB cable to the computer or laptop, You will feel a slight vibration in the tablet.
3: Now you see in the screen that a port is present, so you are now in contact with the Qfil programmer.
4: In the Qfil screen you will see "Select Build Type" choose "Flat Build"
5: At "Select Programmer" press "Browse" choose there prog_firehose_ddr.elf
6: Now press "Load XML" and choose rawprogram_unsparse0 and patch0
7: Now press "Download" the installation will now start so wait until it is finished.
8: After the installation is finished, disconnect the USB connection and restart the tablet:
9: The tablet may start up with the FFBM mode screen, then turn the tablet off again by holding the power button for longer seconds.
10: Start the tablet by pressing the volume - button and the power button.
11: In the screen choose with the volume buttons "Recovery" then in de next screen "Reboot system", the tablet will now start up normally again, this will take a while so wait patiently.
12: Then you come to the welcome screen, this was it and the tablet should now work properly again with the new Android 11 version, good luck!

comtech2005 said:
Download with the Smart Assistant Tool from Lenovo latest firmware version TB_J606F_S320029_210923_ROW.
First Start Qfil.
The Qfil file is where the new firmware by Rescue and Smart Assistant is stored.
For me it was in the folder c:/ProgramData/RSA/Download/RomFiles/ToolFiles/Qfil
1: The tablet must not be connected to the computer and must be off.
2: Now start Qfil, at the top of the screen is now "No Port Available" start now the tablet by holding down the Volume + button and at the same time connecting the USB cable to the computer or laptop, You will feel a slight vibration in the tablet.
3: Now you see in the screen that a port is present, so you are now in contact with the Qfil programmer.
4: In the Qfil screen you will see "Select Build Type" choose "Flat Build"
5: At "Select Programmer" press "Browse" choose there prog_firehose_ddr.elf
6: Now press "Load XML" and choose rawprogram_unsparse0 and patch0
7: Now press "Download" the installation will now start so wait until it is finished.
8: After the installation is finished, disconnect the USB connection and restart the tablet:
9: The tablet may start up with the FFBM mode screen, then turn the tablet off again by holding the power button for longer seconds.
10: Start the tablet by pressing the volume - button and the power button.
11: In the screen choose with the volume buttons "Recovery" then in de next screen "Reboot system", the tablet will now start up normally again, this will take a while so wait patiently.
12: Then you come to the welcome screen, this was it and the tablet should now work properly again with the new Android 11 version, good luck!
Click to expand...
Click to collapse
Hi. I saw your post on Forum Lenovo. I followed your instructions but it failed (ver 210923). Can you make a video tutorial? I want to see where I went wrong.
Thank you!

hungali33 said:
Hi. I saw your post on Forum Lenovo. I followed your instructions but it failed (ver 210923). Can you make a video tutorial? I want to see where I went wrong.
Thank you!
Click to expand...
Click to collapse
Install the QPST file and then go to the bin folder. It contains the QFIL.exe there. Then follow the instructions by comtech2005. Do not install the later version TB-J606F_S320109_211207_ROW.zip. I got stucked in the start/ffbm etc mode. What I did was use QFIL in the QPST folder and then revert to the 210923 ROW. It went smoothly using this qfil version.
As additional info surprise, it prompted me for the 211207 ROW OTA update. Hope this works ok after installing the OTA update.

MSJI said:
Install the QPST file and then go to the bin folder. It contains the QFIL.exe there. Then follow the instructions by comtech2005. Do not install the later version TB-J606F_S320109_211207_ROW.zip. I got stucked in the start/ffbm etc mode. What I did was use QFIL in the QPST folder and then revert to the 210923 ROW. It went smoothly using this qfil version.
As additional info surprise, it prompted me for the 211207 ROW OTA update. Hope this works ok after installing the OTA update.
Click to expand...
Click to collapse
Yup, installing the OTA update takes about 10 minutes and am now on 211207 ROW version.

I have a new China-sourced P11 Pro (TB-J706F) that is now stuck on the bootloader screen. I've tried the Lenovo Rescue and Smart Assistant to install the latest ROM and it fails partway through the fix process. I've also tried the standalone QFIL process with several ROMs for this device - these also quit part way through. Is the device fixable?

GideonS said:
I have a new China-sourced P11 Pro (TB-J706F) that is now stuck on the bootloader screen. I've tried the Lenovo Rescue and Smart Assistant to install the latest ROM and it fails partway through the fix process. I've also tried the standalone QFIL process with several ROMs for this device - these also quit part way through. Is the device fixable?
Click to expand...
Click to collapse
As I have advised, this failed on me too when I used LMSA or the standalone QFIL download. Use the QPST download where it has the QFIL.EXE and then follow instructions in the previous postings.

MSJI said:
As I have advised, this failed on me too when I used LMSA or the standalone QFIL download. Use the QPST download where it has the QFIL.EXE and then follow instructions in the previous postings.
Click to expand...
Click to collapse
Still no luck. Tried on 2 different PCs and with 2 different cables.

GideonS said:
Still no luck. Tried on 2 different PCs and with 2 different cables.
Click to expand...
Click to collapse
What rom version you are installing and what was the previous rom when it was working ok?

MSJI said:
What rom version you are installing and what was the previous rom when it was working ok?
Click to expand...
Click to collapse
I'm embarrased to say I didn't check the ROM version before trying to upgrade to latest ROW. But it's reporting as S620022_210910_ROW in the Android Recovery menu
But I've tried to upgrade to several versions inc..
TB-J706F_S620108_211124_ROW
TB-J706F_S250260_210804_ROW
TB-J706F_S241015_210326_ROW
TB-J706F_CN_WIFI_USER_Q00018.0_Q_ZUI_12.0.335_ST_201103_qpst
Thanks again for your ongoing advice

GideonS said:
I'm embarrased to say I didn't check the ROM version before trying to upgrade to latest ROW. But it's reporting as S620022_210910_ROW in the Android Recovery menu
But I've tried to upgrade to several versions inc..
TB-J706F_S620108_211124_ROW
TB-J706F_S250260_210804_ROW
TB-J706F_S241015_210326_ROW
TB-J706F_CN_WIFI_USER_Q00018.0_Q_ZUI_12.0.335_ST_201103_qpst
Thanks again for your ongoing advice
Click to expand...
Click to collapse
When I encountered an issue in my upgrade, I reverted to the last working ROM using the QFIL.EXE in QPST. It went ok. I have no need to use QFIL since my tablet with the working ROM prompted me for an OTA update. So my understanding is that you upgraded your tablet but you do not know what version you upgraded from. So it could be possible that you downgraded from a newer version?

OMG. Just had a breakthrough. I'd been trying firmware flash with 2 different top-quality USB cables, one of which was the supplied Lenovo cable. But after advice here I bought a dedicated EDL cable. I've just tried it and the Flash took!
{
"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"
}

GideonS said:
OMG. Just had a breakthrough. I'd been trying firmware flash with 2 different top-quality USB cables, one of which was the supplied Lenovo cable. But after advice here I bought a dedicated EDL cable. I've just tried it and the Flash took!
View attachment 5510781
Click to expand...
Click to collapse
That's great!!

(GUIDE:) How to ROOT the TAB S6 - SM-T860 (Wi-Fi Model) - (12/10/21):

Hello all,
BORING INTRO STUFF (Safely Ignore This):
I couldn't find any guide that was current enough to make me feel confident in going through with rooting this tablet. So because of that, I decided I would make on my own guide for those that needed this. I tried multiple guides here and all of them resulted in a boot-loop.
VERY SMALL PSA: I'm apologizing in advance if this guide is both pointless and longer than it needs to be. I figured it would be useful as a future reference in-case anyone needed this.
THINGS YOU WILL NEED:
* TAB S6 - SM-T860 (Wi-Fi)
* This can be done on Android 9,10 & 11 (Process is the same)
* Your specific firmware downloaded (*DO NOT SKIP THIS*)
* Tablet is charged to at least 50%
* Maximum of 20 minutes to both read & follow the process
* FIRMWARE: The link below is the firmware I used. I would still advise you to both look for your specific version and to use the link provided below only if your tablet is exactly as followed:
* (T860XXU4CUI4) - BUILD NUMBER
* (ANDROID 11) - ANDROID VERSION
* (XAR - CELLUAR SOUTH) - SERVICE PROVIDER SOFTWARE VERSION
( https://samfirms.com/SM-T860/KOR/T860XXU4CUI4 )
* SAMSUNG USB DRIVERS: ( https://developer.samsung.com/android-usb-driver )
* ODIN: ( https://samfirms.com/download-odin ) Latest is 3.14.4. Use that one or the newest one
* TWRP (OPTIONAL): T860 (Wi-Fi) ONLY. DOWNLOAD VERSION "twrp-3.6.0_9-0-gts6lwifi.img.tar" OR THE LATEST ONE AVAIABLE.
( https://dl.twrp.me/gts6lwifi/ )
* MAGISK APP: ( https://magiskmanager.com/downloading-magisk-manager )
* LZ4 TOOL: ( https://github.com/lz4/lz4/releases )
* 7-ZIP: ( https://www.7-zip.org/download.html )
HOW TO ROOT:
1. UNLOCKING THE BOOTLOADER: *** THIS WILL WIPE YOUR DATA *** (GO TO SETTINGS > ABOUT TABLET > SOFTWARE INFORMATION & TAP BUILD NUMBER 7 TIMES. GO TO DEVELOPER OPTIONS > TOGGLE ON OEM UNLOCKING) TURN OFF THE TABLET. AT YOUR PC, HAVE A CABLE CONNECTED TO THE PC. WHILE HOLDING BOTH VOLUME DOWN + VOLUME UP, PLUG IN THE CABLE. WHEN THE SCREEN TURNS ON, PRESS AND HOLD VOLUME UP.
WHEN THE SCREEN CHANGES PROMOTING YOU TO UNLOCK THE BOOTLOADER, PRESS VOLUME UP. ONCE BOOTED UP, GO THROUGH THE SETUP AGAIN AND MAKE SURE Wi-Fi IS CONNECTED. GO BACK TO SETTINGS, ENABLE DEVELOPER OPTIONS AGAIN AND THEN ENABLE USB - DEBUGGING.
2. EXTRACT THE BOOT.IMG.LZ4 FILE AND MOVE IT TO YOUR TABLET: After 7-Zip is installed, the LZ4 Tool and the firmware you downloaded is extracted somewhere, open the extracted firmware folder. Right-click on the AP file and select 7-zip then open archive. Look for boot.img.lz4, drag it inside of the LZ4 Tool. Once done, drag the boot.img.lz4 on top of the LZ4 executable. It will be extracted as boot.img. Right-click the boot.img file and select 7-zip then add to archive. Change "Archive format" to tar and rename it to boot.tar. Finally, move it to your tablet's storage.
3. DOWNLOAD THE MAGISK APK: Install the Magisk apk that you downloaded and open it up. Within the app, select install, uncheck recovery mode and press next then check "Select and Patch a file". Locate your boot.tar file that you moved into your storage from earlier and wait for Magisk to process it.
4. USING ODIN: Go ahead and locate the new file, it starts with Magisk (NOT THE BOOT.TAR FROM EARLIER SHOULD START WITH MAGISK). Once done, move the Magisk tar file to your computer and turn off the tablet. With the tablet off and Odin open (Run as administrator) , press and hold both VOLUME DOWN & VOLUME UP then plug the cable from your pc into your tablet. With Odin open, go into the "options" tab, uncheck "Auto Reboot" and Select "AP". Locate the Magisk tar file you moved from your tablet and then press "Start".
ONCE IT SAYS "PASS" THEN STOP AND READ THIS BEFORE CONTINUING. *IMPORTANT*
PRESS AND HOLD BOTH POWER AND VOLUME DOWN FOR 7 SECONDS. THE SCREEN WILL TURN BLACK. VERY QUICKLY WHILE STILL HOLDING POWER, PRESS AND HOLD VOLUME UP INSTEAD. PRESS POWER TO THE BOOTLOADER UNLOCK PROMPT AND YOU SHOULD BE IN RECOVERY. THIS SHOULD BOOT YOU INTO STOCK RECOVERY. USE THE VOLUME KEYS TO NAVIGATE, SELECT "Wipe data/factory reset" then press the power button and select "Factory data reset". Finally, select "Reboot system now" and Wait for the tablet to reboot into the OS.
5. FINISHING UP: After the tablet has restarted back into android and you took a couple of minutes to go through the setup one last time. Scroll up into the app drawer and make sure that you see the app "Magisk", go ahead and select it and press ok to download Magisk. Afterwards, open it up and Magisk will ask you to reboot to finish setting up root. Press ok. Once restarted you are done with the rooting process.
Lastly, as an optional step you can install TWRP.
6. TWRP INSTALLATION (OPTIONAL): With the tablet off and Odin running on your pc, go ahead and press VOLUME DOWN AND VOLUME UP at the same time then plug in the data cable from your PC. Press VOLUME UP to go into download mode. Once in download mode, select "AP" then select the TWRP tar file you downloaded and make sure to uncheck "Auto reboot" from the options tab in Odin. Click start and after it says "PASS" unplug the data cable. On the tablet, press VOLUME DOWN AND POWER to reboot and when you see THE SCREEN TURN BLACK, QUICKLY PRESS AND HOLD BOTH POWER AND VOLUME UP. You should be in TWRP and you are now officially done.
* From now on, I would recommend you use the Magisk app or some reboot app to boot into recovery as it is difficult to use the button combinations to access recovery.
* IF YOU'RE NOT USING MAGISK TO REBOOT TO RECOVERY, I WOULD USE THIS APP INSTEAD: https://play.google.com/store/apps/details?id=com.eypcnnapps.quickreboot&hl=en_US&gl=US
Credits: If all went well then I appreciate you taking the time to read through this guide carefully. Hope it was as clear as possible and that you found it helpful. I will be editing this post from time to time to make it cleaner.
Again, Thank you and if you have any questions, I will answer them when I see them.

THANK YOU SO MUSH IVE BEEN STRUGGLING SO HARD TO GET ROOT ON THIS TABLET FINALLY THANK YOUUUUUU
by the way guys, when it says to reboot to make magisk work.
you are risking a bootloop.

Oh by the way, aside from TWRP being wonky thank you for the guide I had been playing with the idea of rooting this thing for over a year now. You made it easy.
I go through all the steps and it works fine. Once I try for TWRP I end up with
"partition recovery
Reason recovery: Error verifying vbmeta image: invalid vbmeta header (6)
CUSTOM recovery
VBMETA T860XXU4DVG6, 54204454R"
From that point it just loops back to that message and downloading mode until I wipe it all and start over again. I TWRP a no go for the S6 now? I guess I can dig around on their site as well. Any input anyone wants to throw my way will also be appreciated.

Hi Sadistic - ,
I need to start with a complement. This is a really clear guide.
But, When I get done with step 3, the Magisk patched boot file has a .img extension
On step 4, Odin is expecting a .tar file extension so the file doesnt show up.
Did I miss something?
Thanks

mvanwey said:
Hi Sadistic - ,
I need to start with a complement. This is a really clear guide.
But, When I get done with step 3, the Magisk patched boot file has a .img extension
On step 4, Odin is expecting a .tar file extension so the file doesnt show up.
Did I miss something?
Thanks
Click to expand...
Click to collapse
Yep..... try step 2

seppukuudere said:
Yep..... try step 2
Click to expand...
Click to collapse
Yes, step 2 is moving the extracted boot file (re-named to .tar) to my tablet and then patching it with magisk.
The patched file from Magisk has an .img extension.

mvanwey said:
Yes, step 2 is moving the extracted boot file (re-named to .tar) to my tablet and then patching it with magisk.
The patched file from Magisk has an .img extension.
Click to expand...
Click to collapse
Ah I see, I would try to do step 3 again, take screenshots of the end result from magisk o:

Let's just cancell this. it was over 20 days since I asked for help & now I'm getting asked for screenshots.
I have moved on.
I probably should have put that in my reply.

mvanwey said:
Let's just cancell this. it was over 20 days since I asked for help & now I'm getting asked for screenshots.
I have moved on.
I probably should have put that in my reply.
Click to expand...
Click to collapse
oops yikes, yeah probably should have. happy new year!

seems like after rooting mine the storage has been cut by a big margin, from 128 to 32gb. any way of fixing this?
{
"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"
}

Hi. Is there any update guide for last android 12 version, to install twrp? Can se still use this, as it is for android 11?
Thanks,