Well, I found this in a Telegram group (which I know I can't share the link) and when performing all possible tests, it works perfectly with my 4/128 spes.
And as we would all say, I am not responsible for any damage and loss of data caused to your device. I only share the information "as is" and the tests performed by myself on my personal device. Everything is at your own risk.
So, let's start with the post:
New Developer on this version:
@jabieff
Previous Developer
@dblenk9 - Telegram
2022/11/06 Update Changelog:
Synced latest TWRP 12.1 source
Fixed Android 13 ROM flashing issue (source side)
Changelog in the previous version by @dblenk9
Sync with latest TWRP
Update kernel to MIUI V13.0.4.0.SGCMIXM
Update blobs to MIUI V13.0.4.0.SGCMIXM
MTP fixed
Decrypt works
Features I tried and didn't have any problems
Flashing and decrypt data from A13 ROMs
Flashing and decrypt data from A12.1(A12L) ROMs
Flashing and decrypt data from MIUI-based ROMs (custom and Stock) with A12
Flashing Magisk
MTP fully functional
ADB sideload
Install recovery ramdisk and "Flash current TWRP" from Advanced menu
DO NOT USE WITH ANDROID 11 ROMS!!!
Bugs I've found so far
If you perform a format data, the internal memory will not be recognized in MTP mode of TWRP, which will not be displayed in Windows file explorer
SOLUTION: Boot into the OS at least once so that the internal memory is rebuilt and made available again in MTP mode
Sometimes, when checking the option "Automatically reflash TWRP after installing the ROM", it does nothing when it finishes installing the ROM
SOLUTION: The option seems to be somewhat bugged, so before restarting always reinstall TWRP with the methods that I will explain below
When flashing some ROMs, "Failed to mount *partition*" errors come out when you finish installing
SOLUTION: In some ROMs you may get errors when mounting some partitions, commonly "system_ext", "product" and "vendor".
If the installation process ended without any problem and without showing any error code, that's fine, you can restart without problems, This bug has been in all unofficial TWRP for this device
Steps to install
Make sure you have the bootloader unlocked before you start. There are many guides on the internet for that.
Tutorial for Windows only because zero knowledge for Mac and Linux
From PC:
Download the latest platform-tools from the Android developer site and extract the zip in an easily accessible folder
Download the TWRP image file from here, or from the post attachments
SHA256: 8F25AC88628E6D7BC5E29D8572CF4ACA3499B7D626685654B3C4548323B8D591
Restart your device to fastboot mode
Method 1:
Using this adb command if you have USB debugging active on your device
Code:
adb reboot bootloader
Method 2:
- Turn off your device
- After it has completely turned off, press and hold Vol - and the Power button at the same time until the word "FASTBOOT" with orange letters comes out
Method 3:
- Turn off yout device
- Press and hold Vol - button
- Connect the USB cable (previously connected to the PC) to the device and press and hold the button until the word "FASTBOOT" with orange letters comes out
Connect your device to the PC
Open a cmd window in the folder where you extracted the binaries from the zip from step 1
Easy method: Open the folder, and without leaving it, type "cmd" in the address bar of the file explorer and press enter. Command promt will open a window directly in the folder location
Verify that your device is recognized by fastboot using this command
Code:
fastboot devices
If your device has been detected (a serial number followed by the word fastboot), you can continue. Otherwise, check if the drivers are installed correctly, although if you used Mi Unlock and were able to unlock the device correctly on the PC you are using, you should not have problems with that.
- Because this device uses A/B partitions, there is no recovery partition as such, but it is integrated into the "boot" partition. So, first we must boot using the TWRP image.
Type this command in the cmd window, but don't press Enter yet, just type it and leave a space at the end
Code:
fastboot boot_
Don't write the "_". This only indicates the space you should leave at the end.
This is how it should look when you write it:
fastboot boot
Now, drag the image file (twrp-3.7.0.img) to the command window and drop it above the window. This will make you copy your exact location for convenience.
- The result should be this:
Code:
fastboot boot "C:\location\to\your\file\twrp-3.7.0.img"
Quotation marks are only added if the entire location has spaces.
Otherwise, it is displayed without quotation marks.
Press Enter and wait a few seconds. The MI logo will come out, and then the TWRP logo.
DONE! You've started perfectly in TWRP
From the device
NOTE: Only use these steps if you want to have TWRP installed semi-permanently
I said "semi-permanent" because when flashing any ROM, and knowing that the "recovery" is integrated into the "boot" partition, it will be lost after leaving TWRP, so you can follow these steps if you want to avoid loss of TWRP.
If you have easy access to a PC, you can be fine with the boot method. If you don't have easy access to a PC, you can follow these steps.
Method 1
While in the TWRP menu, tap the Advanced button
Now tap on the option "Flash current TWRP"
"Swipe to confirm" and the TWRP installation process will begin
Method 2
While in the TWRP menu, tap the Advanced button
Copy the TWRP image file to the internal memory or SD card from the PC. MTP mode is enabled by default
You can use a USB OTG too
Now tap on the option "Install recovery ramdisk"
Now locate the file and tap on it.
You can use the "Select storage" button to switch between different storages
"Swipe to confirm" and the TWRP installation process will begin
Method 3
While in the TWRP menu, tap the Install button
Copy the TWRP image file to the internal memory or SD card from the PC. MTP mode is enabled by default.
You can use a USB OTG too
Tap on the option "Install image"
Now locate the file and tap on it.
You can use the "Select storage" button to switch between different storage
In the new menu, select "Install recovery ramdisk" and then "Swipe to confirm Flash"
Remember that with the three methods mentioned above you will lose root access (Magisk), so do not forget to flash it again. These steps are also valid to update TWRP if you already had it previously installed.
Conclusion
I did everything I could but I couldn't find the source code for this TWRP, so I'm sorry for that.
05/05/2023
POST
- Link to GDrive fixed
11/11/2022
POST:
- Reverted to previous version as @jabieff TWRP is unable to flash MIUI ROMs due to dynamic partitioning error.
07/11/2022
POST
- Added info about Android 11
- Updated to latest TWRP and new developer
19-10-2022
POST:
- Fixed typo and A11 ROMs info added
Hello and thanks for this tutorial. I tried it on my new red minote 11 and unlike on 3.6.1 TWRP my pin code can't unlock encryption.
It returns :
Code:
Failed to decrypt user 0
Is there a way to solve yhis issue ?
Rom version : MUI global 13013 Stable RGKEUXM
Android version: 11 RKQ1.211001.001
Thanks !
essor-13 said:
Hello and thanks for this tutorial. I tried it on my new red minote 11 and unlike on 3.6.1 TWRP my pin code can't unlock encryption.
It returns :
Code:
Failed to decrypt user 0
Is there a way to solve yhis issue ?
Rom version : MUI global 13013 Stable RGKEUXM
Android version: 11 RKQ1.211001.001
Thanks !
Click to expand...
Click to collapse
I think this version of TWRP works only with MIUI13 A12. You're on A11 version of MIUI13.
essor-13 said:
Hello and thanks for this tutorial. I tried it on my new red minote 11 and unlike on 3.6.1 TWRP my pin code can't unlock encryption.
It returns :
Code:
Failed to decrypt user 0
Is there a way to solve yhis issue ?
Rom version : MUI global 13013 Stable RGKEUXM
Android version: 11 RKQ1.211001.001
Thanks !
Click to expand...
Click to collapse
This recovery is not compatible with Android 11 ROMs. If you need one for A11 specifically, use version 3.6.1
NeoSDAP said:
This recovery is not compatible with Android 11 ROMs. If you need one for A11 specifically, use version 3.6.1
Click to expand...
Click to collapse
Thanks for the answer. I'm a bit confused about this (I'm really not an expert, far from that). My previous phone was a antic galaxy S7 that passed awaysome days ago. With that phone (at the end I was on LOS 19 I think) there was no encryption issue, I installed the TWRP on a Oreo android version ans I never had android version compatibility issues (let say that is TWRP version x was compatible with android version y is was also compatible with android version y-1). It seems to be different with my new redmi note 11.
I also had a backup / restore issue (TWRP 3.6.1) : I did enter the TWRP by unlocking with my pin code, did the backup (data, system and also data+system in case of) and I wanted to restore the data backup (I tried to debloat the ROM via adb but I made some mistakes so I decided to restore the backup data + system) and the TWRP showed a warning : "pin must be desactivated before restoring". I tried to ignore the message (I made enough mistakes to be enable to reach the phone's login), the restore operation failed with an "error 255". So I reconfigured the phone, desactivated the login pin, went to TWRP, made the restore (no pin warning) but hen the phone didn't boot correctly (hanged 15 min on the MI startup logo with the three dots on the bottom, but nothing else happens).
I obviously did the backup / restore operation the wrong way. On my S7 it was very easy : I make a full backup, data+system, then I restore it when needed, and no issue at all). So What is the correct way to backup / restore a full system + data with TWRP without having to do a factory reset and then try to restore Titanium backup (which cannot restore correctly all the apps, some need to be resintalled). This solution works, but it is much longer and annoying than restoring a TWRP/nandroid backup.
Thanks !
@NeoSDAP You could add sth like 'only for A12/A13'-roms to the title and add a highlighted note, that You need 3.6.1 for A11 roms to the OP.
essor-13 said:
Thanks for the answer. I'm a bit confused about this (I'm really not an expert, far from that). My previous phone was a antic galaxy S7 that passed awaysome days ago. With that phone (at the end I was on LOS 19 I think) there was no encryption issue, I installed the TWRP on a Oreo android version ans I never had android version compatibility issues (let say that is TWRP version x was compatible with android version y is was also compatible with android version y-1). It seems to be different with my new redmi note 11.
I also had a backup / restore issue (TWRP 3.6.1) : I did enter the TWRP by unlocking with my pin code, did the backup (data, system and also data+system in case of) and I wanted to restore the data backup (I tried to debloat the ROM via adb but I made some mistakes so I decided to restore the backup data + system) and the TWRP showed a warning : "pin must be desactivated before restoring". I tried to ignore the message (I made enough mistakes to be enable to reach the phone's login), the restore operation failed with an "error 255". So I reconfigured the phone, desactivated the login pin, went to TWRP, made the restore (no pin warning) but hen the phone didn't boot correctly (hanged 15 min on the MI startup logo with the three dots on the bottom, but nothing else happens).
I obviously did the backup / restore operation the wrong way. On my S7 it was very easy : I make a full backup, data+system, then I restore it when needed, and no issue at all). So What is the correct way to backup / restore a full system + data with TWRP without having to do a factory reset and then try to restore Titanium backup (which cannot restore correctly all the apps, some need to be resintalled). This solution works, but it is much longer and annoying than restoring a TWRP/nandroid backup.
Thanks !
Click to expand...
Click to collapse
Because this device uses a different partition scheme (A/B partitions and, apparently, dynamic partitions) it is not necessary to make nandroid backups, since the partitions change size depending on the ROM you install.
If you want to keep everything in order:
- Keep a copy of TWRP and the zip of the ROM you are using to avoid problems in the future.
- If you want a backup of the info on your phone, I recommend you install Magisk and use Swift Backup. It's in the Play Store.
gentano said:
@NeoSDAP You could add sth like 'only for A12/A13'-roms to the title and add a highlighted note, that You need 3.6.1 for A11 roms to the OP.
Click to expand...
Click to collapse
Thanks for the correction. I have already modified the title
NeoSDAP said:
Thanks for the correction. I have already modified the title
Click to expand...
Click to collapse
Can you please tell me if it's possible to flash twrp via magisk app for root access and for installing twrp itself, actually I've updated my rn11 and insalled October security patch but my custom recovery along with root is overwritten
sarib said:
Can you please tell me if it's possible to flash twrp via magisk app for root access and for installing twrp itself, actually I've updated my rn11 and insalled October security patch but my custom recovery along with root is overwritten
Click to expand...
Click to collapse
Nope. You need a PC to install the recovery. Something that can also work is to use a phone rooted with Magisk and the ADB and fastboot module
NeoSDAP said:
Because this device uses a different partition scheme (A/B partitions and, apparently, dynamic partitions) it is not necessary to make nandroid backups, since the partitions change size depending on the ROM you install.
If you want to keep everything in order:
- Keep a copy of TWRP and the zip of the ROM you are using to avoid problems in the future.
- If you want a backup of the info on your phone, I recommend you install Magisk and use Swift Backup. It's in the Play Store.
Click to expand...
Click to collapse
Thanks a lot for those infos. I understand a bit better now.
By any chance do you know a rom (debloated) that works flawlessly (camera, wifi, NFC, BT, etc) with the redmi note 11 ? I had LOS on my S7, that was fine because it made the device last longer, but it wasn't withoutt issues.
am I doing something wrong
Thank.
{
"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"
}
Appl1 said:
War mache ich falsch? Hat jemand eine Idee?
Thank.
View attachment 5779933
Click to expand...
Click to collapse
According to the rules, English is required.
Boot to a different version from TWRP. The v3.62 will help, then flash the v3.7.0 through TWRP. It happens, probably, because some custom recoveries, doesn't allow this version to boot to.
SubwayChamp said:
Gemäß den Regeln ist Englisch erforderlich.
Booten Sie mit einer anderen Version von TWRP. Die v3.62 wird helfen, dann die v3.7.0 über TWRP flashen. Es passiert wahrscheinlich, weil einige benutzerdefinierte Wiederherstellungen es dieser Version nicht erlauben, zu booten.
Click to expand...
Click to collapse
danke werde ich im laufe des tages ausprobieren. Ich habe auf Englisch geschrieben. Verzeihung
Appl1 said:
am I doing something wrong
Thank.
View attachment 5779933
Click to expand...
Click to collapse
Do you have unlocked bootloader?
Appl1 said:
danke werde ich im laufe des tages ausprobieren. Ich habe auf Englisch geschrieben. Verzeihung
Click to expand...
Click to collapse
Thanks for the edit of your first post and the switch to English. However, if you check you post above it's again only in German. Did you check your browser's settings if it automatically translates to German even if you wrote in English?
Regards
Oswald Boelcke
Senior Moderator
sarib said:
Can you please tell me if it's possible to flash twrp via magisk app for root access and for installing twrp itself, actually I've updated my rn11 and insalled October security patch but my custom recovery along with root is overwritten
Click to expand...
Click to collapse
Same ****.. I bought my phone in July... then rooted it... then all these useless security patches for me used to unroot my phone - remove TWRP and the root while have magick app installed. One time tried to reroot and ****ed up so had to reflash again the stock rom (I was with the stock rom before) just lost some data (not a big deal... all apps with their non cloud savable data, settings and etc LOL)
So I am still wondering how to avoid this and properly update without losing the root.
Also when Xiaomi will stop releasing **** small updates every month?
Flammable98 said:
Same ****.. I bought my phone in July... then rooted it... then all these useless security patches for me used to unroot my phone - remove TWRP and the root while have magick app installed. One time tried to reroot and ****ed up so had to reflash again the stock rom (I was with the stock rom before) just lost some data (not a big deal... all apps with their non cloud savable data, settings and etc LOL)
So I am still wondering how to avoid this and properly update without losing the root.
Also when Xiaomi will stop releasing **** small updates every month?
Click to expand...
Click to collapse
There´s not such a thing; "...properly update without losing the root", any major update causes the loss of root, because of boot partition, but, if the update is only about security policies, then you shouldn´t lost root. Rooting this device can always be done, flashing the Magisk zip over the ROM.
Anyway, you can choose, not to update automatically, so, this is up to you, get it or not.
Flammable98 said:
Same ****.. I bought my phone in July... then rooted it... then all these useless security patches for me used to unroot my phone - remove TWRP and the root while have magick app installed. One time tried to reroot and ****ed up so had to reflash again the stock rom (I was with the stock rom before) just lost some data (not a big deal... all apps with their non cloud savable data, settings and etc LOL)
So I am still wondering how to avoid this and properly update without losing the root.
Also when Xiaomi will stop releasing **** small updates every month?
Click to expand...
Click to collapse
There's a new update "November patch" and I'm now thinking what I should do
Related
First thanks to drgravy who compiled this TWRP build for the LG G Pad 8.3 GPE (V510); device name Palman, a link to the official TWRP download page will be posted once the appropriate section for (Palman) has been created.
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
{
"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"
}
Tablet look:
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
DISCLAIMER:
I nor anyone else is responsible for what you do to your device.
but if something goes wrong I will do my best to help
Download:
TWRP 2.6.3.1 V510 Palman
How to flash:
Since this is a GPE Tab simply boot your device into fastboot. Easiest way is to do adb reboot bootloader.
Once booted into the bootloader simply issue this command:
fastboot flash recovery palman.img
Once done reboot into recovery and you should be greeted with TWRP.
CREDITS:
@Dees_Troy and team win for this wonderful recovery
Confirmed working on GPE version.
Unlocok bootloader and flash recovery or you can just do "fastboot boot palman.img" and it will boot in recovery without flashing it (so you get to keep stock recovery in case you need to run an OTA later).
Hi
I get the message "Waiting for the device", so how get the device in fastboot mode?
Thanks
---------- Post added at 11:19 AM ---------- Previous post was at 11:12 AM ----------
Enable usb debugging or check if u have drivers
Enviado do meu GT-I9300 através de Tapatalk
Ver3go said:
Enable usb debugging or check if u have drivers
Enviado do meu GT-I9300 através de Tapatalk
Click to expand...
Click to collapse
Sorry for the dumb question, but where do I get the drivers for the GPE? I used Dalingrin's easy root script for the LGE, but "adb shell" doesn't work with that minimal adb, so I'm assuming I need to grab a different driver?
UPDATE: Still looking for the drivers. I downloaded the latest ADT and had it install the Google USB Driver, but still neither "adb shell" nor "fastboot devices" works properly. Just to answer the obvious question, yes, I've enabled USB Debugging in Developer Options. Any thoughts on how I can get past this hurdle so that I can get to a point where I can root a GPE device?
UPDATE 2: Okay, I figured it out and have GPE all nice and rooted now! Basically just follow the instructions to root a Nexus 5 but use the recovery image on this thread and you should be golden!
The 4.4.2 update just hit my GPE running this recovery and it failed to install saying:
This package is for "palman" devices; this is a "v 500".
Click to expand...
Click to collapse
Is there any easy way to fix that?
SCWells72 said:
The 4.4.2 update just hit my GPE running this recovery and it failed to install saying:
Is there any easy way to fix that?
Click to expand...
Click to collapse
I might have an easy answer for you, give me a few minutes to try it out first.
---------- Post added at 04:32 PM ---------- Previous post was at 04:06 PM ----------
SCWells72 said:
The 4.4.2 update just hit my GPE running this recovery and it failed to install saying:
Is there any easy way to fix that?
Click to expand...
Click to collapse
I think you can do this two ways, flash back to the stock recovery, or just run the stock recovery once from the bootloader. Flashing back to the stock recovery is probably the safest option, however I have an idea if you don't want to have to go back and forth.
Disclaimer, I'm an NOT expert with this so it may not work.....
Ok, for either option you'll need the stock recovery. You can download it from HERE (Stolen from AutoPrime's post).
I recommend putting the update ZIP and recovery image file in a folder of your root path (for me "C:\android\")
Here's my idea, have fastboot just boot the stock recovery once.
Make sure ADB debugging is enabled in "Developer Options"
Connect your USB cable and run
Code:
adb reboot bootloader
Your tablet should reboot and your should see the bootloader screen, once you see the screen run
Code:
fastboot boot C:\android\17-recovery.img
fastboot should show you progress indicator and once it is finished your tablet should see a red exclamation mark. press the power button and then the vol. up button. This should show options 1. Reboot System 2. ADB Sideload, use the volume keys to select adb sideload then press the power key to select.
then
Code:
adb sideload C:\android\a0bd45922b5958a38acef76f577f527268ef90db.signed-KRT16O.L004_user-KOT49H.L004_user_update.zip
I think it will work, not sure if it will keep TWRP or overwrite it. Like I said earlier, I'm not an expert.
SCWells72 said:
The 4.4.2 update just hit my GPE running this recovery and it failed to install saying:
Is there any easy way to fix that?
Click to expand...
Click to collapse
OTA updates are not working with a custom recovery like twrp. Either flash back to stock or wait for the developers to compile and release the updates as zip packages that you can flash from the custom recovery menu. Look what a developer said about this here http://forum.xda-developers.com/showpost.php?p=48150524&postcount=31
I flashed TWRP after applying the latest OTA 4.4.2, and now it won't boot - just reboots into TWRP and has all kinds of errors about not being able to mount /data.
Any ideas for recovering from this?
Screenshot when trying to factory reset: http://i.imgur.com/Zyf1507.jpg
Edit: Had TWRP reformat /data, still nothing.
Archon810 said:
I flashed TWRP after applying the latest OTA 4.4.2, and now it won't boot - just reboots into TWRP and has all kinds of errors about not being able to mount /data.
Any ideas for recovering from this?
Screenshot when trying to factory reset: http://i.imgur.com/Zyf1507.jpg
Edit: Had TWRP reformat /data, still nothing.
Click to expand...
Click to collapse
Odd, I flashed the 4.4.2 OTA after restoring stock recovery, it updated then after the updated I flashed TWRP back, and am having no such issue.
djkinetic said:
Odd, I flashed the 4.4.2 OTA after restoring stock recovery, it updated then after the updated I flashed TWRP back, and am having no such issue.
Click to expand...
Click to collapse
What can we do right now to try to sort this out? I've also started http://forum.xda-developers.com/showthread.php?p=48593224 to help with the recovery process, which I'm sure folks will find useful in the future.
I'm available for any kind of debugging. Could boot.img have gotten messed up somehow?
Archon810 said:
What can we do right now to try to sort this out? I've also started http://forum.xda-developers.com/showthread.php?p=48593224 to help with the recovery process, which I'm sure folks will find useful in the future.
I'm available for any kind of debugging. Could boot.img have gotten messed up somehow?
Click to expand...
Click to collapse
I have an idea, looking at your screenshot it looks like a similar error that occurred on the N5 and TWRP early on after unlocking the bootloader...After you updated 4.4.2 and then did fastboot oem unlock, did you let the tab boot up? Because after you do that it sets a flag to format the system ext4 on first boot, if you flash a recovery before that happens and boot into recovery first you get errors....do this in recovery delete the file .twrps in /sdcard/TWRP use the file manager advanced...this is the TWRP settings file, once you do that then try to reboot system.
The problem is /sdcard/TWRP/ is completely empty. There are no files in there. I even checked using shell and ls -al.
And yeah, I didn't let it reboot after unlocking.
I actually have a replacement en route from Google to address a yellow tinted display. I think I'll wait until that gets here, let it update to 4.4.2, and then go through this process on that device.
sorry, how do you open the recovery?
djkinetic said:
I have an idea, looking at your screenshot it looks like a similar error that occurred on the N5 and TWRP early on after unlocking the bootloader...After you updated 4.4.2 and then did fastboot oem unlock, did you let the tab boot up? Because after you do that it sets a flag to format the system ext4 on first boot, if you flash a recovery before that happens and boot into recovery first you get errors....do this in recovery delete the file .twrps in /sdcard/TWRP use the file manager advanced...this is the TWRP settings file, once you do that then try to reboot system.
Click to expand...
Click to collapse
djkinetic, can you take a look at this reply? http://forum.xda-developers.com/showpost.php?p=48613367&postcount=10. Could it be that TWRP isn't accounting for something and it needs to do a little extra cleanup to reset a flag somewhere?
I've fastboot formatted cache and userdata already to no avail.
Archon810 said:
djkinetic, can you take a look at this reply? http://forum.xda-developers.com/showpost.php?p=48613367&postcount=10. Could it be that TWRP isn't accounting for something and it needs to do a little extra cleanup to reset a flag somewhere?
I've fastboot formatted cache and userdata already to no avail.
Click to expand...
Click to collapse
I'm probably earlier in the process than you @Archon810. I have similar issues have a decreasing feeling that I will solve this any time soon. At this point, if I fastboot boot the recovery palman.img and try to install the noroot V510 zip image provided, I get the binary link error which was present on my Nexus 7 on twrp for awhile. I backleleveled the twrp to 2.6.3.0 on the Nexus 7 and this stopped that problem. More seriously, after all the stuff I've done to fix things, I fear I have probably borked things more than fixed them.
Now after any attempt at flashing anything in recovery whether I install the recovery or just boot from it, the result is binary file error.
Going to try restoring the default image and doing things again.
Archon810 said:
djkinetic, can you take a look at this reply? http://forum.xda-developers.com/showpost.php?p=48613367&postcount=10. Could it be that TWRP isn't accounting for something and it needs to do a little extra cleanup to reset a flag somewhere?
I've fastboot formatted cache and userdata already to no avail.
Click to expand...
Click to collapse
Flash the stock recovery from here http://downloads.codefi.re/autoprim...Firmware/KRT16O_16_partitions/17-recovery.img
Then reboot in recovery see if it continues the format process from unlocking the BL
Sent from my LG-G2 using Tapatalk
Any way we can get a CWM build for V510 so that we can avoid the binary error from TWRP?
djkinetic said:
Flash the stock recovery from here http://downloads.codefi.re/autoprim...Firmware/KRT16O_16_partitions/17-recovery.img
Then reboot in recovery see if it continues the format process from unlocking the BL
Sent from my LG-G2 using Tapatalk
Click to expand...
Click to collapse
Yeah, as per the other thread, this did the trick.
Team Win Recovery Project 3.1.1-0
This is for the A2017, A2017U, and A2017G.
WARNING: The ZTE Axon 7 stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Follow the full rooting steps below in order to allow system modifications without the risk of a boot loop!
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
Read more about TWRP here: https://twrp.me/about/
DOWNLOAD
You can find the device page here:
http://teamw.in/devices/zteaxon7.html
There is a download link there, as well as instructions on how to flash it.
You can find up to date fastboot & adb binaries here!
UNLOCKING YOUR BOOTLOADER
WARNING: Unlocking your bootloader will erase all userdata on the device! Your device will be completely reset to factory defaults!
A2017U or A2017 users can simply unlock from EDL mode using MiFlash here.
I do not have a method for A2017G, there may be other threads on XDA to guide you through the process.
FULL STEPS FOR OBTAINING ROOT
Follow these instructions until someone nice comes along and makes a video from them (without ads):
Unlock your bootloader! See above!
{
"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"
}
Download TWRP for the ZTE Axon 7.
Reboot your device into fastboot mode. To do this, select reboot from the power menu and hold the [Volume Up] button while your device reboots or boots from power off.
Once you're in fastboot with your bootloader unlocked, you're ready to flash TWRP. To do this, run the command (replacing twrp.img with the actual image name):
fastboot flash recovery twrp.img
Once the image is flashed, you should use your volume keys to navigate to RECOVERY and the press the power key to select it.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
If you want to be rooted with SuperSU:
Download the latest SuperSU stable by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
---or (not both) ---
If you want to be rooted with Magisk:
Download the latest Magisk stable by topjohnwu.
Without exiting TWRP, transfer the Magisk zip to your device over MTP* and flash it using [Install] in TWRP.
---or (not both) ---
If you want to be rooted with something else or just want a bootable system:
Download the latest dm-verity and forced encryption disabler zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
This will also allow you to use [Format Data] to completely disable your encryption if desired.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up. (SuperSU will reboot you a few times)
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
UPDATING TWRP
To update TWRP, simply download the new twrp.img on your phone, then boot into your current TWRP and flash it.
To flash a twrp.img, navigate to [Install] -> [Flash Image] -> select your twrp.img -> [x] Recovery -> Flash!
After that, just use [Reboot] -> [Recovery] to reboot into the updated TWRP.
CHANGES
v3.1.1-0 (twrp.me) - See release details here!
v3.1.0-0 (twrp.me) - See release details here!
v3.0.4-1 (build.nethunter.com) - Fix crash on selecting reboot with an empty data partition, add Data backup warnings
v3.0.4-0 (build.nethunter.com) - Capability restoration for Nougat, F2FS backport support, EXT4 decryption support
v3.0.3-1 (twrp.me) - Use crypto libraries from ROM (Nougat support). Fix USB OTG and Fast Charging. Reduce boot times.
v3.0.3-0 (twrp.me) - Renamed to ailsa_ii, Persist merged with EFS, Modem no longer mounted, Backup/Restore/Flash Bluetooth/System Image added. LA.HB.1.3.1.c1-19500-8x96.0 + Linux 3.18.45.
v3.0.2-0 (twrp.me) - Initial release.
FEATURES
MTP support
USB OTG storage support
Legacy USB Mass Storage mode support - use your phone like an SDCard reader or flash drive!
Hardware Qualcomm-based full-disk encryption support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
Allows ZTE full OTA flashing (only for A2017U firmware)
KNOWN ISSUES
F2FS takes a long time to boot, see below.
WHY DOES F2FS MAKE TWRP SO SLOW?
When TWRP boots up or wipes partitions and a few other scenarios, it checks each partition to see how much disk space is used. Ext4 handles disk usage calls quite efficiently and will finish this very fast. F2FS on the other hand is very slow when it comes to checking disk usage. We're unsure why this is. Every file on the F2FS formatted partition adds a little more time, and a device that is 30 GB full could take up to 10 minutes to boot TWRP!
I suggest switching your data partition to ext4 - all the f2fs hype is merely from benchmarks that don't actually represent real world use (ie. you're not writing thousands of files per second)
For someone who doesn't do lots of write access to their data partition, ext4 can actually be advantageous (it has faster access times and reads!)
HOW DO I GET LOGS SO WHEN I COMPLAIN I'M NOT COMPLETELY IGNORED OR SHAMED BY OTHER USERS?
To get logs while in TWRP, you should connect your device to your PC and use adb.
adb pull /tmp/recovery.log
adb exec-out dmesg > dmesg.log
This will create 2 files in the directory your shell is currently in, recovery.log and dmesg.log. You will need to upload these somewhere such as a pastebin or Google Drive. You can also attach it to your XDA post (recommended!)
If you are having an operating system boot issue, you should gather a ramoops log instead. Do this while in TWRP after the failed boot:
adb exec-out "tar c /sys/fs/pstore 2>/dev/null" > pstore.tar
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-7.1)
Device tree: https://github.com/TeamWin/android_device_zte_ailsa_ii (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_oneplus_msm8996 (twrp-6.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
Team Win Recovery Project for the ZTE Axon 7, Tool/Utility for the ZTE Axon 7
Contributors
jcadduono, Team Win
Source Code: https://github.com/TeamWin/android_device_zte_ailsa_ii
Version Information
Status: Stable
Current Stable Version: 3.0.4-1
Stable Release Date: 2017-02-08
Created 2016-12-09
Last Updated 2017-11-25
Link does not work is there a typo?
lokissmile said:
Link does not work is there a typo?
Click to expand...
Click to collapse
Nope, bigbiff is just taking long time to hit the go button on jenkins to build the device and rebuild twrp.me lol
I think he fell asleep
You can use this for now: https://build.nethunter.com/test-builds/twrp/zte/twrp-3.0.2-0-a2017u.img
Downloaded and installed although not sure how this differs from the one in the unlock thread. Made a backup everything seems OK. Thanks!
lafester said:
Downloaded and installed although not sure how this differs from the one in the unlock thread. Made a backup everything seems OK. Thanks!
Click to expand...
Click to collapse
It shouldn't be any different, or any differences there are should be minimal.
One (and maybe only) notable difference might be that it uses ZTE's USB configuration rather than Google's.
It also supports legacy mass storage. (accessing sdcard like a flash drive, instead of MTP)
I should also add that it's pretty much 1/3 of the size too lol.
UnjustifiedDev's unofficial TWRP is 3.0.2-2. I recall people were having issues with restoring some partitions (mostly EFS), so he backported the bugfix from the 7.0 TWRP code, which seemed to have fixed the issues. Does this official build include that bugfix?
Is there any technical reason why this version shouldn't be installed on A2017G?
xtermmin said:
UnjustifiedDev's unofficial TWRP is 3.0.2-2. I recall people were having issues with restoring some partitions (mostly EFS), so he backported the bugfix from the 7.0 TWRP code, which seemed to have fixed the issues. Does this official build include that bugfix?
Click to expand...
Click to collapse
That bug was fixed in September on the 6.0 branch.
_phk_ said:
Is there any technical reason why this version shouldn't be installed on A2017G?
Click to expand...
Click to collapse
I don't have any technical reason, just from what I've read it won't boot. You can try it, let me know what happens. Actually please do, because if it does boot it would be quite pleasing and I'd end up unifying them.
Is this TWRP using the stock B29 kernel or your custom Kernel?
I was building my own TWRP for the Axon-7 the other day. Mainly to include more partitions for backup purpose while working on CM and back to stock. (Especially persist).
As far as I saw the CM rom messes with persist (creates folders and files in persist).
Should ZTE release Android 7.0 in January I want to be able to go back using the backup created of B29 and simply run the OTA.
If CM messes with persist and one goes back to B29 to upgrade to Android 7. The OTA partitions check before upgrade will probably fail with checksum errors. And the upgrade will fail.
One would have to go all the way back to factory B20 then =>B27 =>B29=>Android 7.
Correct me if I'm wrong.
But shouldn't we include at least those partitions that CM touches in TWRP for proper restore possibilities? And future upgrades of Stock?
celoxocis said:
...If CM messes with persist and one goes back to B29 to upgrade to Android 7. The OTA partitions check before upgrade will probably fail with checksum errors. And the upgrade will fail...
Click to expand...
Click to collapse
So far, none of the OTAs (at least for the US model) have done a check of persist, but who knows if they will for Nougat.
celoxocis said:
Is this TWRP using the stock B29 kernel or your custom Kernel?
I was building my own TWRP for the Axon-7 the other day. Mainly to include more partitions for backup purpose while working on CM and back to stock. (Especially persist).
As far as I saw the CM rom messes with persist (creates folders and files in persist).
Should ZTE release Android 7.0 in January I want to be able to go back using the backup created of B29 and simply run the OTA.
If CM messes with persist and one goes back to B29 to upgrade to Android 7. The OTA partitions check before upgrade will probably fail with checksum errors. And the upgrade will fail.
One would have to go all the way back to factory B20 then =>B27 =>B29=>Android 7.
Correct me if I'm wrong.
But shouldn't we include at least those partitions that CM touches in TWRP for proper restore possibilities? And future upgrades of Stock?
Click to expand...
Click to collapse
It uses a custom very minimal kernel configuration with modifications to make it more compatible with TWRP.
Why does modification of persist matter? Persist can't affect OTAs as it's meant to be modified, it's only a firmware/calibration cache.
If it ever had an issue you could simply type:
make_ext4fs /dev/block/bootdevice/by-name/persist
CM should not modify any partitions that are meant to be static.
The only partitions that will need to be fixed to take OTAs should be: boot, system, recovery, modem (NON-HLOS.bin)
The only reason modem needs to be fixed is because it's used in TWRP and I can't enable both backup and read-only at the same time.
Update: I'll just make two entries, backup/restore for raw modem emmc, and read-only mount for decrypt. (should be safe to do this with mounttodecrypt unmounting it)
xtermmin said:
So far, none of the OTAs (at least for the US model) have done a check of persist, but who knows if they will for Nougat.
Click to expand...
Click to collapse
They will not. There is no logical reason to check a partition that is designed to be modified.
In fact, I'll add Persist (calibration data) to the Wipe page!
jcadduono said:
It uses a custom very minimal kernel configuration with modifications to make it more compatible with TWRP.
Why does modification of persist matter? Persist can't affect OTAs as it's meant to be modified, it's only a firmware/calibration cache.
If it ever had an issue you could simply type:
make_ext4fs /dev/block/bootdevice/by-name/persist
Click to expand...
Click to collapse
Thanks for the clarification. I just remember when I was dirty flashing CM13 months ago when doing one of my devices bring-up. TWRP would complain with error 7 (I think?).
When I run a diff of the partitions it touched (I checked all init.rc's) I found the difference in persist. Reverting back the persist with DD (I always do a DD backup of my untouched devices, on all partitions before messing with them and store them on my NAS). The dirty flash went fine. Ever since that I include persist in my TWRP's.
I don't mind not having it in TWRP. I can bake my own anytime
celoxocis said:
Thanks for the clarification. I just remember when I was dirty flashing CM13 months ago when doing one of my devices bring-up. TWRP would complain with error 7 (I think?).
When I run a diff of the partitions it touched (I checked all init.rc's) I found the difference in persist. Reverting back the persist with DD (I always do a DD backup of my untouched devices, on all partitions before messing with them and store them on my NAS). The dirty flash went fine. Ever since that I include persist in my TWRP's.
I don't mind not having it in TWRP. I can bake my own anytime
Click to expand...
Click to collapse
I just replaced the -0 version, new one has modem read only and persist shows up in wipe page as "Persist (calibration data)" so people know what they're wiping.
There's a lot of partitions that seem scary and screw up your device when they're corrupt but you can just either format them (in the case of persist) or dd zeros to them (in the case of misc, modemst1, modemst2, efsg, and efsc) and the OS/firmware will regenerate everything on boot like you just took it out of the box.
any reason to flash this version of TWRP over the one UnjustifiedDev's made?? I can just flash the twrp.img file right?
celoxocis said:
Is this TWRP using the stock B29 kernel or your custom Kernel?
I was building my own TWRP for the Axon-7 the other day. Mainly to include more partitions for backup purpose while working on CM and back to stock. (Especially persist).
As far as I saw the CM rom messes with persist (creates folders and files in persist).
Should ZTE release Android 7.0 in January I want to be able to go back using the backup created of B29 and simply run the OTA.
If CM messes with persist and one goes back to B29 to upgrade to Android 7. The OTA partitions check before upgrade will probably fail with checksum errors. And the upgrade will fail.
One would have to go all the way back to factory B20 then =>B27 =>B29=>Android 7.
Correct me if I'm wrong.
But shouldn't we include at least those partitions that CM touches in TWRP for proper restore possibilities? And future upgrades of Stock?
Click to expand...
Click to collapse
I was under the impression that you couldn't install OTAb updates with an unlocked bootloader anyway. Is this not true?
abdi7451 said:
I was under the impression that you couldn't install OTAb updates with an unlocked bootloader anyway. Is this not true?
Click to expand...
Click to collapse
Bootloader status hasn't been checked by the OTAs so far (on the US model anyway). I've been able to go from a bootloader unlocked B20 -> official B27 OTA -> TWRP+CM13 -> Restore my B27 backup in TWRP + reflash stock recovery -> official B29 OTA -> reflash TWRP+CM13. As long as you are completely stock besides the bootloader, you can apply OTAs fine. (you can check the updater script in the OTA files for specifics on what it checks and what it patches)
xtermmin said:
Bootloader status hasn't been checked by the OTAs so far (on the US model anyway). I've been able to go from a bootloader unlocked B20 -> official B27 OTA -> TWRP+CM13 -> Restore my B27 backup in TWRP + reflash stock recovery -> official B29 OTA -> reflash TWRP+CM13. As long as you are completely stock besides the bootloader, you can apply OTAs fine. (you can check the updater script in the OTA files for specifics on what it checks and what it patches)
Click to expand...
Click to collapse
I am rooted and unlocked bootloader. How do apply the stock recovery in order to receive OTA updates?
Just wanna clarify this... B20 bootloader allows the fastboot OEM unlock command, and once you're unlocked, you can flash any bootloader you want. Flashing B29 bootloader does not lock you, once unlocked, always unlocked. Unless you relock it yourself. You can even go older than B20 bootloader. Feel free to play around with BL versions. I like B20 because no stupid 5 second warning thing.
If I already have the unofficial version for TWRP should I install this one over it or is it really the same thing?
@jcadduono, I think most people would find it helpful if you could list what's different between the now official version and @Unjustified Dev's version, as I know they've been developed semi in parallel.
Team Win Recovery Project 3 ver 3.0.3 RAYGLOBE
{
"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"
}
This has been tested and working great on LON-L29 international. It will work on all mate 9 pro devices, however I added a list of supported devices below which can be checked.
[COLOR="Red"]WARNING #1[/COLOR]: Unlocking BL and flashing a custom recovery voids your warranty. Please make sure to contact your carrier/seller if your phone is still under warranty after unlocking the bootloader.
[COLOR="red"]WARNING #2:[/COLOR] Make sure you have enabled OEM unlock and unlocked bootloader before trying to flash this. How you can successful root and install TWRP will be described below.
[COLOR="red"]WARNING #3:[/COLOR] Nougat introduce dm-verity v2.0 so before modify /system make a backup of partition and flash root (see above).
[COLOR="red"]WARNING #4:[/COLOR] Don't make factory reset inside TWRP on Huawei device.
[SIZE="3"]
[SIZE="3"]
WHAT IS TWRP?[/SIZE]
TWRP, short for Team Win Recovery Project, is an open-source recovery image for Android-based devices. It provides a touch-enabled interface which allows users to install third-party firmware and backup the current system, which are often unsupported by stock recoveries.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
[SIZE="5"]HOW-TO INSTALL[/SIZE]
0. Make sure you enabled OEM unlock in settings, if you haven't please do that now by tipping 10 times on build number (to activate developer options), than open developer options and go to OEM unlock, enable it
1. Have an unlocked bootloader is required!
2. Download the TWRP recovery from the download section below
3. Make sure you got fastboot drivers installed (I will describe this below in how to unlock your bootloader)
4. Open the adb/fastboot application on your pc and go to the directory where your TWRP img file is downloaded
5. Boot your phone into download mode (First method: fastboot reboot-bootloader while connected to pc. Second method: power off your phone, hit power on and volume down until it boots to download mode)
6. Check again if there is written: UNLOCKED phone! and frp UNLOCKED
7. If yes type now into your adb/fastboot terminal: fastboot flash recovery Rayglobe_Recovery.img
8. Type: fastboot reboot
9. Now boot into recovery by pressing: power+volume up+volume down at the same time
10. Enjoy twrp
[SIZE="4"]HOW-TO UNLOCK BOOTLOADER[/SIZE]
1. Call Huawei in the HiCare app, request the bootloader unlock code there or Buy credit on dc-unlocker software
2. Install minimal adb and fastboot drivers from here: [URL="http://forum.xda-developers.com/showthread.php?t=2317790"]ADB and Fastboot drivers[/URL]
3. Plug in your phone and make sure all huawei drivers got installed
4. Enable developer options in settings as described above.
5. Enable OEM unlock, enable USB debugging (both in developer options)
6. Open the adb tool you installed recently
7. Type fastboot devices (now a device number should show up)
8. Type fastboot reboot-bootloader (your phone will now boot into bootloader, if not, you haven't set up drivers or adb/fastboot correctly)
9. [COLOR="Red"]This step will wipe all your data![/COLOR] Type: fastboot oem unlock xxxxxxxxxxxxxxxx (xx is for your unlock code)
10. Ones it's done type: fastboot reboot. Your phone will reboot and you have an unlocked bootloader!
11. You can now go on installing TWRP on your device
[SIZE="4"]
HOW-TO ROOT YOUR MATE 9 PRO[/SIZE]
0. Backup, just in case
1. Have an unlocked bootloader and TWRP installed from above
2. We will use this root method: [URL="http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394"]Phh's superuser[/URL]
3. Download only this zip (i adapted for mate 9) [URL="https://www.androidfilehost.com/?fid=529152257862699355"] superuser zip [/URL]
4. Put the zip on your otg-usb (since we can't access /data in twrp)
5. Boot into twrp and flash the downloaded file
6. Install latest Material phh apk: [URL="http://forum.xda-developers.com/showpost.php?p=69224582&postcount=1896"]Release post[/URL]
7. Now you are rooted, congrats!
[SIZE="4"]FEATURES[/SIZE]
Built in android 7.1 tree
Support .sh script so you can install phh root without problems
Latest stock kernel included
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format, backup & restore)
Full SELinux support
[COLOR="Red"]KNOWN ISSUES[/COLOR]
Encryption is not supported yet! I hope that @paulobrien can share his sources as soon as possible
We can't save twrp settings
Factory reset delete data/hw_init directory so make backup if you want themes and original apps
Aroma is broken, seems on all other Huawei phones
[SIZE="4"]SUPPORTED DEVICES[/SIZE]
LON-L29
LON-AL00
[SIZE="5"]
DOWNLOAD[/SIZE]
[URL="https://www.androidfilehost.com/?fid=457095661767133388"] TWRP IMAGE FILE[/URL] ---> FLAT VER
[URL="https://www.androidfilehost.com/?fid=457095661767133388"] TWRP IMAGE FILE[/URL] ---> THEMED VER
Last ver
v3.0.3 -1.0.7.
[HIDE]
[img]http://i.imgur.com/iWqWAnYh.png
[/HIDE]
XDA:DevDB Information
[Recovery][Root][02.05.2017] Huawei Mate 9 Pro * Unofficial TWRP for all LON models , Tool/Utility for the Huawei Mate 9
Contributors
raimondomartire, Tkkg1994, LastStandingDroid
Source Code: https://github.com/Tkkg1994/android_device_generic_a15
Version Information
Status: Stable
Created 2017-01-29
Last Updated 2017-02-05
FAQ
Q. HOW TO ROOT?
A. https://forum.xda-developers.com/showpost.php?p=70867589&postcount=101
Great work as usual bro,thanks for your time and job :good:
raimondomartire said:
Factory reset delete data/hw_init directory so make backup if you want themes and original apps
Click to expand...
Click to collapse
Just my 2 cents. When you did factory reset / wipe data from TWRP, phone will not boot anymore.
TWRP clears whole data partition
But Huawei links additional things (hw_init, custom.bin and etc...) to /data partition, which stock recovery does not clear.
So advice: Never do wipe data / factory reset from TWRP
5[Strogino] said:
Just my 2 cents. When you did factory reset / wipe data from TWRP, phone will not boot anymore.
TWRP clears whole data partition
But Huawei links additional things (hw_init, custom.bin and etc...) to /data partition, which stock recovery does not clear.
So advice: Never do wipe data / factory reset from TWRP
Click to expand...
Click to collapse
Yes mate agree with you I put a script to avoid this. I don't know if really work. A lot of mods in twrp 3.0.3 that i must test
raimondomartire said:
Yes mate agree with you I put a script to avoid this. I don't know if really work. A lot of mods in twrp 3.0.3 that i must test
Click to expand...
Click to collapse
Need find way install official Roms (ota or full) via twrp without errors. Unfortunately, without kernel sources it will be very hard.
5[Strogino] said:
Need find way install official Roms (ota or full) via twrp without errors. Unfortunately, without kernel sources it will be very hard.
Click to expand...
Click to collapse
Yes we must ask Huawei respect GPL or use xda developers power for it
some user write me in PM that recovery work good also on mate 9 (flat version).
I removed sdcard from .fstab files for mate pro 9 users (we don't have sdcard) so you must use otg usb
raimondomartire said:
some user write me in PM that recovery work good also on mate 9 (flat version).
I removed sdcard from .fstab files for mate pro 9 users (we don't have sdcard) so you must use otg usb
Click to expand...
Click to collapse
And what's difference with Tkkg1994's build for Mate 9 users?
5[Strogino] said:
And what's difference with Tkkg1994's build for Mate 9 users?
Click to expand...
Click to collapse
Good question, but before do you read first post?
In short:
- with my recovery you can flash phh root without problem and use old .sh script
- have .sh script that make a factory reset. On huawei factory reset must be avoid
- have right partition for mate 9 pro
- have right kernel
- have right script to manage brightness inside recovery
:good:
Update first post with zip file to hack dm verity with root
raimondomartire said:
Good question, but before do you read first post?
In short:
- with my recovery you can flash phh root without problem and use old .sh script
- have .sh script that make a factory reset. On huawei factory reset must be avoid
- have right partition for mate 9 pro
- have right kernel
- have right script to manage brightness inside recovery
Click to expand...
Click to collapse
Yep, i've read)
My question is about support Mate 9 users (not Pro)...
It links to "some user write me in PM that recovery work good also on mate 9 (flat version)."
In general, it is safer to use Tkkg1994's build cause it has right kernel
But if you're added some extra features, may be it's better to share them with Tkkg1994 ?
5[Strogino] said:
Yep, i've read)
My question is about support Mate 9 users (not Pro)...
It links to "some user write me in PM that recovery work good also on mate 9 (flat version)."
In general, it is safer to use Tkkg1994's build cause it has right kernel
But if you're added some extra features, may be it's better to share them with Tkkg1994 ?
Click to expand...
Click to collapse
For this reason I avoid to put sdcard line to avoid to disturb Tkkg1994's work. I'm on telegram group with him and other friends. I'm waiting that Paulobrien release decrypt sources to update my github. In this way everyone that contribute to this :good:
raimondomartire said:
Update first post with zip file to hack dm verity with root
Click to expand...
Click to collapse
Congratulations)
Btw, i recommend to delete string in script (changes.sh) that changes RO to RW on all secured partitions by default (system, cust, vendor and etc...)
It would be better if user will mount system partition by button or anything else...
I can modify every partition which is without tag "verify" - tested and approved)
And there is one string in fstab.hi3660
Code:
/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inline_data,inline_xattr wait,check,fileencryptioninline
Code from changes.sh does not know about "fileencryptioninline".
Probably, if add in changes.sh code that will remove this tag, so /data partition will not be encrypted. But i did not test yet.
5[Strogino] said:
Congratulations)
Btw, i recommend to delete string in script (changes.sh) that changes RO to RW on all secured partitions by default (system, cust, vendor and etc...)
It would be better if user will mount system partition by button or anything else...
I can modify every partition which is without tag "verify" - tested and approved)
And there is one string in fstab.hi3660
Code:
/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inline_data,inline_xattr wait,check,fileencryptioninline
Code from changes.sh does not know about "fileencryptioninline".
Probably, if add in changes.sh code that will remove this tag, so /data partition will not be encrypted. But i did not test yet.
Click to expand...
Click to collapse
I agree with you. In boot.img i can confirm you that without tag "verify" you can modify everythings Please if update here if you modify changes.sh. Thanks for your feedback
Excuse me if this is a dumb question: It seems that there have been successes using the other TWRP for mate 9 (the other thread in this forum) for mate 9 pro version already, so what's has been improved here?
One thing missing from the other TWRP is the ability to write to system partition hence half of the root apps are non functioning, eg. busy box, ad away, ... Does this one fixed the problem?
offall said:
Excuse me if this is a dumb question: It seems that there have been successes using the other TWRP for mate 9 (the other thread in this forum) for mate 9 pro version already, so what's has been improved here?
One thing missing from the other TWRP is the ability to write to system partition hence half of the root apps are non functioning, eg. busy box, ad away, ... Does this one fixed the problem?
Click to expand...
Click to collapse
Yes, already post this answer before. Yes my twrp work for this. here a tes ver. for mate 9. Flash my zip ver. in first thread for root
https://www.androidfilehost.com/user/?w=settings-dev-files&flid=149142
Tried the link but have to have an account to access it. Also to clarify are you saying that by flashing your test version of twrp and your root method that we can have a writable system? If so that's great
Sent from my MHA-L09 using XDA-Developers Legacy app
New backup/restore structure partitions (more stable)
https://www.androidfilehost.com/?fid=673368273298928161
raimondomartire said:
New backup/restore structure partitions (more stable)
https://www.androidfilehost.com/?fid=673368273298928161
Click to expand...
Click to collapse
Dear Ray, a beer: Confirmation number: 71T12250HF2138003 to thank you for your fantastic job, done in the pure spirit of XDA.
And now, if you're going to keep the phone at least 2-.3 months, we'll be waiting finally for a custom ROM if possible, or at least for a stock ROM flashable using TWRP, avoiding new absurd "taxes" to update...
Team Win Recovery Project
Exynos variants such as International (F), International Dual(Hybrid)-SIM (F/DS), Korean (N) ONLY.
In NO way it is compatible with Snapdragon variants including but not limited to American(U/U1/A/T/P/V), Chinese(0/8/6), Hong Kong(0), Japanese(SC-*), Canadian(W) variants.
#include <std_disclaimer.h>
{
"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"
}
Special Notes:
1. READ THE GUIDE.
2. KNOX will be tripped once you flashed custom binaries to your phone.
(Your warranty may be voided. However, this may not affect you if your country, European Union, for example, forces Samsung to provide hardware warranty regardless of software status.)
More Infos: https://en.m.wikipedia.org/wiki/Rooting_the_Android_operating_system
3. Samsung Firmware OTA (aka System Updates) will no longer work once you flashed custom binaries.
(You can flash custom ROMs if you want to keep the OS up-to-date.)
4. It is HIGHLY UNRECOMMENDED to purchase any access to any kind of private forums, ROMs or Kernels.
(DO NOT GET FOOLED.)
5. You HAVE to use newer version of Odin (>3.13) if you want to flash stock ROMs.
Download:
Galaxy S9:
https://twrp.me/samsung/samsunggalaxys9.html
Galaxy S9+:
https://twrp.me/samsung/samsunggalaxys9plus.html
Sources:
https://github.com/TeamWin
Changelog:
Check #2.
Guide:
Check #3.
Official Telegram Group: - Discussion, Testing, Feedback and Support
Invite Link
Show your appreciation:
Click Thanks!, Rate 5-star or/and Donate to me.
To contribute:
TWRP Code Review
Github pull requests will be ignored.
XDA:DevDB Information
TWRP for Galaxy S9 and S9+, Tool/Utility for the Samsung Galaxy S9+
Contributors
jesec
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Created 2018-03-15
Last Updated 2018-08-15
Changelog:
Note that this page only includes device-specific changes. For global TWRP changes, go to twrp.me.
Apr 18, 2018 (twrp-3.2.1-2):
Refactor USB configurations (fixes ADB)
Remove /cpefs from filesystem table (fixes /cpefs warning/error)
Rebase Kernel to ARCC. (fixes I/O performance issues)
Use correct OTG mount path
Enable software encryption support (general AOSP only, Samsung method remain unsupported)
Mar 16, 2018 (twrp-3.2.1-1):
Add system_image, vendor_image
Rename display name of /odm to "Carrier Configs"
Mar 15, 2018:
USB connection fixes
Mar 14, 2018:
Initial version
Guides:
Be aware that Android Verified Boot requires data (including those in internal storage) to be cleared after you unlocked bootloader and flash custom binaries. ("to protect user data, all state transitions wipe the data partitions and ask the user for confirmation before data is deleted." - https://source.android.com/security/verifiedboot/verified-boot)
It is normal to get prompts like "Integrity verification failed. You have to reset the device to factory settings."
However, this will only happen when there is "state transition" so only when you switch from locked to unlocked or vice versa.
Since Android O, Samsung introduced a new security feature, Remote Mobile Manager (RMM) aka Remote Lock Control (RLC). This feature allows stronger theft protection but unfortunately it also imposes a burden on users like you.
Samsung added a 7-day buffer period for enterprises or device owners to spot a missing/rogue device so they can use this feature to lock the device remotely.
In this 7-day (Prenormal) period, you can NOT flash any custom binaries including but not limited to this TWRP. OEM Unlock option won't appear, either.
(You will meet "custom binary blocked due to remaining installment balance" or "custom binary not allowed" error when you try)
The 7-day timer will start/reset once you completed the setup wizard. After 7 days (168 hours), RLC service will send an inquiry to Samsung's server. If your device is "clean", the RMM state will become "Normal".
Then you can enable "OEM Unlock" option and flash TWRP. Be careful, DO NOT reboot to a stock ROM before you flash patch in part 2 of this guide or you will have to go through another
Whether you have RMM problem or not depends on your model, region and/or carrier.
If you don't have any wait period to enable OEM Unlock option, congratulations but please do NOT mislead other people.
NOT EVERYONE IS AS LUCKY AS YOU.
If you don't have RMM problem when you get the device, it is unlikely that you will get any RMM problems later.
But note that this problem applies to MAJORITY of people.
Note that the special patch will freeze RMM, FRP and OEM lock state.
This is an anti-stupid measure to prevent careless users from enabling security measures which are not compatible with custom binaries.
Part 1 - HOW-TO FLASH TWRP:
1. In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
2. Go to Settings, remove all Samsung and Google accounts and if your device is registered to an enterprise, de-register it.
3. Go to Settings -> Developer options and enable OEM Unlock option.
Notice: This is "state transition" mentioned eailier.
NOTE: You will be asked to do a factory reset, that's normal.
BUT DO NOT LET IT COMPLETE THE WHOLE RESET PROCESS.
You should take a look at the whole guide and be prepared to use reboots as chances to flash or reboot into TWRP.
4. Download and Install Samsung Mobile Phones Drivers.
- Option 1: Download and Install Smart Switch for PC.
- Option 2: Download and Install standalone driver package.
5. Download and extract Odin (Samsung's Flash Tool) to your computer.
6. Download a .tar image of TWRP.
7. Reboot your device to download mode.
- Hold [VOLUME DOWN] + [BIXBY] + [POWER] for approx. 15 seconds.
- Read the warning carefully.
- If you agree, press [VOLUME UP] to get into Download mode. If you don't agree, STOP.
8. Open Odin and place that TWRP tar file in the [AP] slot.
9. Connect your phone.
10. Hold [VOLUME UP] + [BIXBY] + [POWER] on your phone and then press start on Odin.
11. Wait for the phone to reboot. DO NOT release [VOLUME UP] + [BIXBY] + [POWER] or you may not reboot into TWRP.
Part 2 - HOW-TO INITIALIZE TWRP:
1. If you completed Part 1 successfully, you should be in TWRP now. At this point, you will reach the screen asking you if you want to allow system modifications.
2. Select "Keep /system RO".
3. Go to "Wipe" menu of TWRP and you will find "Format Data". Press "Format Data" and type "yes" to continue.
4. Go to "Reboot" menu and Press "Recovery" to reboot TWRP.
5. Download the special dm-verity and force encryption disabler zip on your computer.
6. Transfer the zip to your phone.
- Option 1: MTP: Connect your phone with computer and just copy the zip to internal storage. (similar to how you transfer files when in system.)
- Option 2: ADB: Connect your phone with computer and run command "adb push /path/to/zip /sdcard/".
- Option 3: External SD: Copy the zip to an external SD and then insert the card to your phone.
7. Go to "Install" menu of TWRP and flash the zip.
TWRP is initialized and fully functional at this stage.
Now you may want to flash a root solution (Magisk, SuperSU, etc) or custom ROM but keep in mind that:
1. This thread does NOT provide technical support to any root solution or ROM unless the problem is DIRECTLY related to TWRP and there is no other solution without modifying TWRP itself.
Please contact developer of respective ROM or root solution for technical support.
2. Samsung implemented security measures such as "Real-time Kernel Protection (RKP)" and "RKP Control Flow Protection". https://www.samsungknox.com/en/blog/real-time-kernel-protection-rkp
Those security measures are intended to block control flows such as privilege escalation, memory kernel code modification, etc which are not authorized by Samsung.
If those are not disabled, processes (such as daemon of root solutions) that violated those security rules will fall into deadlock.
Deadlocked processes will then consume large amount of resources (leads to performance issues, battery drains) and eventually crash the system.
Technically it is possible to disable those security measures by hex editing stock kernel but just simply flash a custom kernel is better in my opinion.
TL;DR: Flash custom kernel before root or be screwed.
Awesome work Jesse. Thank you!
Has anybody flash it on a galaxy s9+?
Gesendet von meinem SM-G950F mit Tapatalk
@jesec hey mate, happy to see you again (S7 ROM)
Sorry i don't have this device but my friend will try soon
spackeddie01 said:
Has anybody flash it on a galaxy s9+?
Gesendet von meinem SM-G950F mit Tapatalk
Click to expand...
Click to collapse
I did try it on my Exynos S9+ but it didnt work. Maybe im doing something wrong. Odin says PASS! Then the S9+ reboots but hangs on: Verification error. Cant reboot device. The integrity verification didnt succeed. U have to reset the device to factory settings. Bla bla bla. And the option to reset. By the way, my device os is in dutch so i did try to translate the notification on the screen of the phone.
BokkieAndijk said:
I did try it on my Exynos S9+ but it didnt work. Maybe im doing something wrong. Odin says PASS! Then the S9+ reboots but hangs on: Verification error. Cant reboot device. The integrity verification didnt succeed. U have to reset the device to factory settings. Bla bla bla. And the option to reset.
Click to expand...
Click to collapse
Please boot to recovery instead of system.
Be aware that Android Verified Boot requires data to be cleared after you unlocked bootloader and flash custom binaries. ("to protect user data,*all*state transitions wipe the data partitions and ask the user for confirmation before data is deleted." - https://source.android.com/security/verifiedboot/verified-boot) It is normal to get such prompt.
Got twrp installed formatted data, rebooted twrp, do we need Dm-Verity? If so how to get it on as MTP is not working, or OTG, and system bootloop so can't get back in to do it that way.
BokkieAndijk said:
I did try it on my Exynos S9+ but it didnt work. Maybe im doing something wrong. Odin says PASS! Then the S9+ reboots but hangs on: Verification error. Cant reboot device. The integrity verification didnt succeed. U have to reset the device to factory settings. Bla bla bla. And the option to reset. By the way, my device os is in dutch so i did try to translate the notification on the screen of the phone.
Click to expand...
Click to collapse
You have to flash dm-verity/magisk.
****! I think i did something very wrong. When i want to reboot system in TWRP it says: are you sure u like reboot the system? N OS installed.
iamnotkurtcobain said:
Awesome work Jesse. Thank you!
Click to expand...
Click to collapse
Dis you try treble AOSP ?
giorgior.r said:
Dis you try treble AOSP ?
Click to expand...
Click to collapse
I can't. This TWRP is for 9+. I have a normal S9.
---------- Post added at 10:11 AM ---------- Previous post was at 10:09 AM ----------
BokkieAndijk said:
****! I think i did something very wrong. When i want to reboot system in TWRP it says: are you sure u like reboot the system? N OS installed.
Click to expand...
Click to collapse
You formated system it seems.
Steps are:
-flashing TWRP
-boot into TWRP
-format Data
-reboot recovery
-install magisk
-reboot
iamnotkurtcobain said:
You have to flash dm-verity/magisk.
Click to expand...
Click to collapse
pls can you give me a link to the packages you have used?
Thanks.:good:
Nice to see you doing work on the S9 @jesc
deleted
@jesc good to see you in the s9 forums. Great work as usual
Where can i find a stock rom for my Dutch (Netherlands) S9+? I think thats the only sollution for my bootloop.
BokkieAndijk said:
Where can i find a stock rom for my Dutch (Netherlands) S9+? I think thats the only sollution for my bootloop.
Click to expand...
Click to collapse
check in this site
https://www.sammobile.com/firmwares/database/SM-G965F/
Flashed twrp then flashed no dm verity - seemed to flash ok - but saw one error message that says "failed to mount '/cpefs' - I haven't seen that error before but thought it might be important. THis message happens after the flash has finished -(after it says updating partician details)
Tried to flash magisk after I flashed twrp and phone bootloops had to flash stock in odin
Root Instructions for SM-T290 (Samsung Galaxy Tab A 8.0 2019)
{
"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"
}
Welcome! This is my first guide on XDA Developers. This will tell you how to root a Samsung Galaxy Tab A 8.0 2019, specially for the SM-T290 model of it. I hope you like it and it works! It has exactly 30 steps.
Disclaimer
* Your warranty will or is now be void. It might already been void (if your warranty is over...)
* I'm not responsible for any damage to your device when following this guide. It's your choice to do it.
* If you still say it's my fault, I'll probably say that I had warned you.
Click to expand...
Click to collapse
UPDATE YOUR TABLET TO VERSION T290XXU3CVG3 AND NOT HIGHER!!!Please update your tablet to the version listed above and NOT higher. Make sure it is fully upgraded to Android 11, so that you can use the better version of TWRP. BUT NOT HIGHER THAN THE VERSION ABOVE, AS THE DEVICE WILL LIKELY NEVER BE ABLE TO BE ROOTED AGAIN. Update by flashing T290XXU3CVG3 with Odin. Download the firmware for your country. Soon I might will update this guide so that TWRP will work on the latest firmware, but for now, DO NOT GO HIGHER THAN T290XXU3CVG3!!! If you have bootloader version 4, it is impossible to flash any of the stuff described here and your device won't be able to have a downgraded bootloader, making it currently impossible to flash any custom stuff when you have bootloader version 4!
MAKE A BACKUP!Be sure to make a complete backup first of all important stuff you have! When you have TWRP (and likely also ROOT), you are able to make a COMPLETE backup of your tablet, including partitions like boot and data and allows apps with complete data to be restored, be sure to use this feature when you have installed TWRP.
Known issues
Charging the device while it is powered off will power it on again. The device will always be on when charging.
Sometimes, when you wipe and/or format data, the storage space is seen as 8GB, while it has 32GB. You can find the fix here.
The battery may drain fast. If this is your case, check this fix.
You may get a black screen after you have flashed TWRP. This means that this method likely doesn't work for your device, because your device came with Android 10 instead. This means that the Android 9 bootloader doesn't work properly on this device. We know the device can be used by using screen mirroring from ADB, but we need more research.
Issue trackerYou can report issues here. This repository is used to report issues for all my XDA threads. You MUST add the label 'Root Instructions For SM-T290', so I know where to post this issue.
Instructions for ROOT1. Power on your device.
2. Open the settings app.
3. Go to 'About device/phone/tablet'
4. Click on 'Software info'.
5. Tap on the build number for 7 times until a message pops up saying "You are now a developer!".
6. Go back to home menu of settings app and click on 'Developer options'.
7. Enable the OEM unlock switch.
Optional: Unlock the bootloader using the steps below, go through setup, enable developer options and check if the option is still enabled.
8. Turn your device off and reboot into download mode by plugging the device into a PC using an USB cable and holding Pwr+VolUp+VolDown after being plugged in.
9. Disable the OEM lock and enable bootloader by holding VolUp for 10 seconds and then follow the instructions.
10. After that, you should see a download icon saying (downloading...).
11. Download Odin Flash Tool 'Odin3-v3.14.4.zip' from the files below.
12. Extract the ZIP file.
13. Open the ODIN executable.
14. Connect your tablet with a micro-USB to USB-A adapter (Your charging cable).
15. Download TWRP recovery image by clicking here. It should work with any version on your tablet. (TWRP XDA Thread)
16. Go back to ODIN, click OK.
17. Go to 'options' tab.
18. Disable 'Auto Reboot'. (not required, keeping enabled may be needed if you can't install and/or use the device.)
19. Click the check box before 'AP'.
20. Click on 'AP'.
21. Select the TWRP file 'twrp-3.7.0_11-0-T290XXU3CVG3-20221120.tar.md5'.
For users with auto-reboot enabled: read step 22, 23 and 24 first to do it correctly.
22. Click 'start'.
23. Wait until you see 'PASS' in the left upper corner.
24. READ THIS WHOLE STEP BEFORE YOU EXECUTE IT! On your tablet, hold the Pwr+VolDown button for 10 seconds until it reboots. From then, you need to be fast. When you see the logo, hold Pwr+VolUp. When you see a warning, IMMEDIATELY press ONLY Pwr for once. After that, hold Pwr+VolUp again as fast as you can until you see the TWRP logo. You successfully managed to install custom recovery! If you fail, you must redo step 16-18 until you get into TWRP.
25. Swipe the box to the right so that you can make modifications and can install Magisk (App for ROOT) and Multidisabler (Disables VaultKeeper, so that ROOT and TWRP will not be uninstalled after normal boot).
26. On the computer, download 'Magisk-v25.2.apk' from here and 'multidisabler-samsung-3.1.zip' from below (under thread), and copy these 2 files to the root directory of the tablet's internal storage by selecting the tablet in Windows Explorer, selecting 'Internal Storage' and pasting them there. If you see weird directories, you may need a SD card connected to the tablet and paste the file there, which was my case. For SD card, you are going to select 'SD Card' instead of 'Internal Storage'.
27. Press 'Install' on tablet.
28. If you have an SD Card, click 'Select storage' and click on '(micro)SD Card'. Select 'Magisk-v25.2.apk' and then swipe to install. Wait until this is done. After that, repat step 21-22 for 'multidisabler-samsung-3.1.zip' and do the same, but this time, also click 'Wipe cache/dalvik' afterwards to make sure it can build new, fresh cache.
29. When you are done, click 'Done'.
30. Click 'Reboot' and then 'System'.
Hooray! You have rooted your SM-T290 tablet successfully. You can close/exit everything now! The app for root is 'Magisk', so verify that you have root completely by opening it, and looking at the 'Installed' column in the 'Magisk' section. If it says 'Installed 25.2 (252XX)', and ROOT is succesfully installed! If it doesn't say this, reboot into TWRP and repeat step 21-22.
(Maybe edited so please stay tuned.)
TWRP image could not be upload here due to XDA not allowing me to upload it due to the .tar.md5 file extension.
Recommended TWRP flashable ZIPs
Open Gapps - Replaces/Installs more up-to-date apps from Google: https://opengapps.org
Samsung Game Services (by me) - Installs Samsung Game Booster + Launcher + Optimizing Service on any Samsung device with OneUI: https://github.com/minionguyjpro/Samsung-Game-Services-Installer
TroubleshootingProblem: 8GB on a 32GB device
Fix: Turn your device off, boot into TWRP by holding Pwr+VolDown, pressing Pwr once immediately on the warning prompt, and pressing Pwr+VolDown again, until you boot into TWRP. Then go to Wipe > Advanced Wipe > Select System > Repair or Change File System > Resize File System > Swipe to the right. If that doesn't work, you can also try the Data partition, and/or the other option 'Repair File System'.
Problem: Fast battery drain
Fix: Turn your device off, boot into TWRP by holding Pwr+VolDown, pressing Pwr once immediately on the warning prompt, and pressing Pwr+VolDown again, until you boot into TWRP. Then go to Wipe > Advanced Wipe > Select Dalvik / ART Cache > Swipe to Wipe. If that doesn't work, try to factory reset the device, look for apps that may cause a fast battery drain or use a Custom ROM that is faster and has a better battery life.
Offline instructions and dataThe offline guide and data are also available below:
Couple points of note:
To enter recovery mode, hold Volume UP (+), not Down (-). Do not hold Power, it will force a reboot again.
After unlocking the bootloader, the best course of action is to allow the device to boot into Android and enable Developer Options, then check to ensure OEM Unlocking is still there and grayed out (should show Bootloader is already unlocked). If not, this may cause problems when attempting to flash TWRP. See here
TWRP 3.6.0_11 is here: XDA Thread Download link
It's not necessary to change the Magisk extension from .apk to .zip. TWRP will still install it as a ZIP.
The only acceptable source for Magisk is the Magisk Github
It is not necessary to use an SD card, although it's recommended given the tablet's limited storage. MTP should work while in TWRP; the user can transfer both Magisk and the Multidisabler to the internal storage via USB and install them before wiping data.
V0latyle said:
Couple points of note:
To enter recovery mode, hold Volume UP (+), not Down (-). Do not hold Power, it will force a reboot again.
After unlocking the bootloader, the best course of action is to allow the device to boot into Android and enable Developer Options, then check to ensure OEM Unlocking is still there and grayed out (should show Bootloader is already unlocked). If not, this may cause problems when attempting to flash TWRP. See here
TWRP 3.6.0_11 is here: XDA Thread Download link
It's not necessary to change the Magisk extension from .apk to .zip. TWRP will still install it as a ZIP.
The only acceptable source for Magisk is the Magisk Github
It is not necessary to use an SD card, although it's recommended given the tablet's limited storage. MTP should work while in TWRP; the user can transfer both Magisk and the Multidisabler to the internal storage via USB and install them before wiping data.
Click to expand...
Click to collapse
While you say SD is not required, on mine my internal storage had random dirs. And didnt show files so i needed SD, but that depends of someone else has this too.
Minionguyjpro said:
While you say SD is not required, on mine my internal storage had random dirs. And didnt show files so i needed SD, but that depends of someone else has this too.
Click to expand...
Click to collapse
That's normal. TWRP is unable to decrypt storage, so the random directory names are because everything is scrambled. Still, you should be able to transfer files to internal storage via USB; just put them in the root of internal storage. The files you transfer will be unencrpyted.
That being said, it IS easier to use an external SD card...
V0latyle said:
TWRP 3.6.0_11 is here: XDA Thread Download link
Click to expand...
Click to collapse
According to this link, the file twrp-3.6.1_11-0-T290XXU3CUK4-20220327.tar.md5, which includes 4 files: recovery.img (actually TWRP), vaultkeeper.mbn, vbmeta.mbn and finally the file aboot.mbn, and this android bootloader 9 T290XXS3ATF1. That is, when installing TWRP, the android bootloader 11 is replaced with the android bootloader 9 ... Naturally, then we get a positive result
Talich52 said:
According to this link, the file twrp-3.6.1_11-0-T290XXU3CUK4-20220327.tar.md5, which includes 4 files: recovery.img (actually TWRP), vaultkeeper.mbn, vbmeta.mbn and finally the file aboot.mbn, and this android bootloader 9 T290XXS3ATF1. That is, when installing TWRP, the android bootloader 11 is replaced with the android bootloader 9 ... Naturally, then we get a positive result
Click to expand...
Click to collapse
Interesting. I'm getting set up now after installing CVG3, I'll update when done.
Edit: Yep, bootloader version shows as T290XXU3CVG3. I'll flash TWRP and update when done.
V0latyle said:
Interesting. I'm getting set up now after installing CVG3, I'll update when done.
Click to expand...
Click to collapse
Pay attention to the bootloader version. This is clearly visible in the Phone Info application in the Firmware Information tab...
V0latyle said:
Couple points of note:
To enter recovery mode, hold Volume UP (+), not Down (-). Do not hold Power, it will force a reboot again.
After unlocking the bootloader, the best course of action is to allow the device to boot into Android and enable Developer Options, then check to ensure OEM Unlocking is still there and grayed out (should show Bootloader is already unlocked). If not, this may cause problems when attempting to flash TWRP. See here
TWRP 3.6.0_11 is here: XDA Thread Download link
It's not necessary to change the Magisk extension from .apk to .zip. TWRP will still install it as a ZIP.
The only acceptable source for Magisk is the Magisk Github
It is not necessary to use an SD card, although it's recommended given the tablet's limited storage. MTP should work while in TWRP; the user can transfer both Magisk and the Multidisabler to the internal storage via USB and install them before wiping data.
Click to expand...
Click to collapse
OK, great!
Talich52 said:
According to this link, the file twrp-3.6.1_11-0-T290XXU3CUK4-20220327.tar.md5, which includes 4 files: recovery.img (actually TWRP), vaultkeeper.mbn, vbmeta.mbn and finally the file aboot.mbn, and this android bootloader 9 T290XXS3ATF1. That is, when installing TWRP, the android bootloader 11 is replaced with the android bootloader 9 ... Naturally, then we get a positive result
Click to expand...
Click to collapse
Yes, it does still work.
Talich52 said:
Pay attention to the bootloader version. This is clearly visible in the Phone Info application in the Firmware Information tab...
Click to expand...
Click to collapse
Yes, I understood you the first time.
V0latyle said:
Couple points of note:
To enter recovery mode, hold Volume UP (+), not Down (-). Do not hold Power, it will force a reboot again.
After unlocking the bootloader, the best course of action is to allow the device to boot into Android and enable Developer Options, then check to ensure OEM Unlocking is still there and grayed out (should show Bootloader is already unlocked). If not, this may cause problems when attempting to flash TWRP. See here
TWRP 3.6.0_11 is here: XDA Thread Download link
It's not necessary to change the Magisk extension from .apk to .zip. TWRP will still install it as a ZIP.
The only acceptable source for Magisk is the Magisk Github
It is not necessary to use an SD card, although it's recommended given the tablet's limited storage. MTP should work while in TWRP; the user can transfer both Magisk and the Multidisabler to the internal storage via USB and install them before wiping data.
Click to expand...
Click to collapse
I made a few changes. VolDown and VolUp are now correct. And removed Magisk and changed to direct download link from GitHub.
Talich52 said:
Pay attention to the bootloader version. This is clearly visible in the Phone Info application in the Firmware Information tab...
Click to expand...
Click to collapse
This should be no issue if you have Android 11. I installed it this exact way while i already had Android 11. I think the bootloader just gets a different version. I have latest T290XXU3CVG3 version with the android 9 bootloader from that TWRP version.
Minionguyjpro said:
This should be no issue if you have Android 11. I installed it this exact way while i already had Android 11. I think the bootloader just gets a different version.
Click to expand...
Click to collapse
Turns out flashing TWRP does overwrite the bootloader.
After updating via Odin, I was at T290XXU3CVD3.
After flashing TWRP, it's at T290XXS3ATF1.
Talich52 said:
Pay attention to the bootloader version. This is clearly visible in the Phone Info application in the Firmware Information tab...
Click to expand...
Click to collapse
Is no
V0latyle said:
Yes, I understood you the first time.
Click to expand...
Click to collapse
First flash update, then flash only AP with TWRP. Make sure to disable auto-reboot.
V0latyle said:
Turns out flashing TWRP does overwrite the bootloader.
After updating via Odin, I was at T290XXU3CVD3.
After flashing TWRP, it's at T290XXS3ATF1.
Click to expand...
Click to collapse
Yes, maybe that the bootloader is overwritten. But this is only a issue if you want the latest security patches. But i have the latest version of Android 11 installed. May it be possible that the software will be updated, but the bootloader/firmware will stay on an older version?
V0latyle said:
Turns out flashing TWRP does overwrite the bootloader.
After updating via Odin, I was at T290XXU3CVD3.
After flashing TWRP, it's at T290XXS3ATF1.
Click to expand...
Click to collapse
Yes, that's why it works. And the author of the TWRP file modestly kept silent that he was changing the bootloader to Android 9 ...
There is no trouble in this, the device is fully functional on Android 11 with 9 bootloader. One trouble - charging does not work, more precisely, there is no display of charging when charging the switched off device. This is critical for someone, but I don’t turn off the device, it only blocks ...
Minionguyjpro said:
May it be possible that the software will be updated, but the bootloader/firmware will stay on an older version?
Click to expand...
Click to collapse
A rooted device will not be updated over the air or via SmartSwitch. But you can update the firmware via ODIN, saving the data. But the bootloader should remain 9 android ...
Talich52 said:
Yes, that's why it works. And the author of the TWRP file modestly kept silent that he was changing the bootloader to Android 9 ...
There is no trouble in this, the device is fully functional on Android 11 with 9 bootloader. One trouble - charging does not work, more precisely, there is no display of charging when charging the switched off device. This is critical for someone, but I don’t turn off the device, it only blocks ...
Click to expand...
Click to collapse
Works for me
Minionguyjpro said:
Yes, maybe that the bootloader is overwritten. But this is only a issue if you want the latest security patches. But i have the latest version of Android 11 installed. May it be possible that the software will be updated, but the bootloader/firmware will stay on an older version?
Click to expand...
Click to collapse
Talich52 said:
A rooted device will not be updated over the air or via SmartSwitch. But you can update the firmware via ODIN, saving the data. But the bootloader should remain 9 android ...
Click to expand...
Click to collapse
Samsung devices are a bit weird. On "proper" devices like my Pixel, you can force update system without updating bootloader or radio. Not sure if Samsung works the same way; I suppose someone could try only flashing AP, CP, CSC and see if it works?
V0latyle said:
Works for me
Samsung devices are a bit weird. On "proper" devices like my Pixel, you can force update system without updating bootloader or radio. Not sure if Samsung works the same way; I suppose someone could try only flashing AP, CP, CSC and see if it works?
Click to expand...
Click to collapse
The weird thing is that you need to flash TWRP as AP, not BL. Indeed the charging will turn the device on.this issues is listed in the thread.
Minionguyjpro said:
The weird thing is that you need to flash TWRP as AP, not BL. Indeed the charging will turn the device on.this issues is listed in the thread.
Click to expand...
Click to collapse
Yeah...so updating will always overwrite TWRP. My theory is by not flashing the BL tar, maybe it won't overwrite the older bootloader?
V0latyle said:
Yeah...so updating will always overwrite TWRP. My theory is by not flashing the BL tar, maybe it won't overwrite the older bootloader?
Click to expand...
Click to collapse
Could be. Im not really sure. But... is the root workimg?