Related
[GUIDE] OOS v4.0.3 ---> FLASH & ROOT STOCK -OR- CUSTOM ROM WITH EASE & CORRECTLY
If you think that I need to add more information to this guide, please post your request. I'm not able to guess what you want from me to add to this guide.
Thank you!
INTRODUCTION:
This guide is mainly for users who tried flashing OxygenOS v4.x.x the easy and short way (like in post #9 in this thread), which had issues in the process.
I covered the most common issues with flashing OOS v4.x.x in this guide. However, you can use this guide to flash OxygenOS (latest Stable and Beta versions)
and root them OR flash your custom ROM. Just follow the instructions.
Now, you ask “why I decided to write this guide?”. Well here’s my story:
I had FreedomOS v1.7 with Google apps installed (including Dialer and Contacts from OpenGApps), encrypted, official twrp (v3.0.2-1), Xposed (v3.1.1), framework (v87),
AdAway v3.2, YouTube AdAway and SuperSU v2.79 (stable). Also, stock kernel, no Dolby ATMOS or A.R.I.S.E apps.
So, when OOS v4.0 came out, I waited for FreedomOS v2.0 to come out too. Once it did, I downloaded the ROM, OpenGApps, modified twrp .28 and started
the flashing process (I backed up my data first).
First, I flashed twrp .28 (had no problems booting into it), and clean flashed FOS v2.0. I selected “Yes” in “Pin/Pattern backup in data partition”, so I wouldn’t have issues with encryption. I selected the regular apps (for OOS to work properly) and installed the OS.
When it was done, I rebooted the device to the OS. I was confused with the new “dm-verity” message popping from nowhere, but the OS booted successfully.
When I rebooted to the twrp (to install OpenGApps), it asked for a password. I couldn’t enter the right password, because it wouldn’t accept any and it blocked
my access to my internal storage.
I started panicking, looking for answers, and I was afraid that I bricked my phone. However, after some research, I calmed down. I realized that my bootloader was still working and could roll back to OOS v3.2.8 (with stock recovery), which I did. From there I flashed FOS v1.7 and waited for more information about the new Nougat update for OnePlus 3.
Now, I’m using Stock OygenOS v4.0.3 with Stock Kernel (see FAQ #16) and so far, no issues (no dm-verity message or password upon entering modified twrp).
I tried to repeat the dm-verity issue and fixed it (see FAQ #6). I was so frustrated that no one posted a proper guide on how to fix these issues, or they were too advanced. I didn’t want to mess around with the core of the system too much. Therefore, I decided to post a simple-to-follow guide.
DISCLAIMER & IMPORTANT:
I am not responsible for any damages done by this guide. You are tinkering with your phone and held responsible for that. This is not an advanced guide. Therefore, I will refer you to the advanced guides when needed. Furthermore, this guide is based on the issues that I and other users encountered while
flashing OOS v4.x.x ------------>***BACK UP PERSONAL DATA BEFORE PROCEEDING ANY FURTHER***
This guide is intended for owners of OnePlus 3. But, after some poking in OnePlus 3T forums, you can use this guide. The only differences the OnePlus 3T
have are a newer processor, newer front camera and a different color from OnePlus 3. Make sure to use the appropriate tools (Stock recovery, TWRP,
OxygenOS v4.0.3, etc.) for OnePlus 3T. Again, I will not be responsible for any damages caused by this guide.
Please follow this guide to get rid of: dm-verity, encrypted twrp, encrypt or decrypt your device (as OnePlus 3 comes encrypted by default), change your file system from EXT4 to F2FS (vice versa as well). Also, flash a Marshmallow or Nougat Stock OOS (Stable or Beta versions), root them OR unroot your device, OR flash a custom ROM.
As far as I know, tested and read in forums, Android v6.0.1 (OxygenOS v3.x.x) supports only EXT4 file system, and Android v7.0 (OxygenOS v4.x.x) supports both EXT4 and F2FS file systems. However, F2FS is recommended for Android v7.0 (OxygenOS v4.x.x). When you perform, a full factory reset in OxygenOS v4.x.x, the file system changes from EXT4 to F2FS. ONLY “Data (userdata)” is affected by this. If you want to go back to Marshmallow, OxygenOS v3.x.x will change your file system from F2FS to EXT4 when you sideload it.
OxygenOS v4.0.3 still comes with some issues, bugs, and some rooting services are not fully supported yet (i.e. Xposed for Nougat). Luckily, OnePlus released kernel sources of Nougat, and we need to wait a little longer for Xposed and other rooting services to be supported. Therefore, I advise staying away from it,
for a little while, until those issues are fixed, and new ones don’t pop up. Also, until rooting apps are fully supported. Follow OnePlus community forums and
XDA forums for updates, troubleshooting, and solutions for your issues. MAKE SURE TO BACK UP YOUR PERSONAL DATA, time to time.
Before posting questions or issues or requests, check FAQ and posts in this thread. Thank You!
WHAT WILL YOU NEED?
You don't need to download everything in this section, only what you prefer to roll with.
ADB drivers installed on your computer (I have version 1.0.32 installed)
Unlocked bootloader (if you haven't done it yet, follow this guide: https://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733)
DiskInfo app from the Play Store:
https://play.google.com/store/apps/details?id=me.kuder.diskinfo&hl=en
OxygenOS v3.2.8 OTA:
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_3.2.8/
OxygenOS v4.0.3 OTA:
https://www.androidfilehost.com/?fid=457095661767136075 OR http://otafsc.h2os.com/patch/amazon...ygen_16_OTA_041_all_1702081756_0f1e56a75f.zip
*** Download speeds might be slow. Be patient. ***
OxygenOs Beta 11 (Nougat):
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_openbeta_11/
Stock Recovery v2.0 (compatible with OOS v3.x.x and OOS v4.x.x):
http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img
Official TWRP (v3.0.2-1 for OxygenOS v3.x.x ; v3.0.3-0 for OxygenOs v4.x.x):
https://twrp.me/devices/oneplusthree.html
Unreleased Official TWRP v3.0.4-1 for Nougat (OxygenOS v4.x.x): *** Recommended for Nougat ***
https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391
Unofficial TWRP (v3.0.3-0 for LineageOS v14.1):
https://forum.xda-developers.com/oneplus-3/development/recovery-twrp-3-0-2-0-touch-recovery-t3402999
Modified TWRP v3.0.3-x blu_spark v16 from @eng.stk:
https://forum.xda-developers.com/devdb/project/dl/?id=23082
SuperSu v2.79 (Stable):
https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
OpenGApps (latest version):
http://opengapps.org/
Your desired custom ROM (I tested FreedomOS v1.7 and v2.3 and v2.4-CE, Experience ROM v10.1 [Stable and Beta 11], LineageOS v14.1):
https://forum.xda-developers.com/oneplus-3/development/rom-freedomos-1-0-t3409348 (FreedomOS - Stable [v1.7 - OOS v3.2.8 ; v2.3 - OOS v4.0.2])
https://forum.xda-developers.com/oneplus-3/development/rom-freedomos-ce-1-7-t3470660 (FreedomOS - Beta [v2.4-CE - OOS Beta 11])
https://forum.xda-developers.com/oneplus-3/development/rom-experience-rom-v1-0-t3522259 (ExperienceOS - Stable and Beta 11 [v10.1])
https://forum.xda-developers.com/oneplus-3/development/rom-cyanogenmod-14-1-oneplus-3-t3496850 (LineageOS v14.1 - based on Andriod v7.1.1)
Code:
[I][SIZE="4"][B] * I'LL BE USING OOS v4.0.3, OFFICIAL UNRELEASED TWRP v3.0.4-1 AND FreedomOS
v2.3 AS AN EXAMPLE FOR THIS GUIDE. OTHER VERSIONS OF OOS AND TWRP
(PROVIDED) ARE APPLICABLE TO BE USED IN THE GUIDE (ONLY WHAT I TESTED).
[COLOR="Red"][I] * If you don't have dm-verity issue, file system change issue or password
upon entering TWRP, then go to Section C (FLASHING YOUR CUSTOM ROM)
-OR- Section D (FLASHING AND ROOTING STOCK OOS OR UNROOT).
* If you do have dm-verity issue, file system change issue or password upon
entering TWRP, then continue to Section A (DM-VERITY).[/I][/COLOR]
[/B][/I][/SIZE]
A - PROCEDURE (DM-VERITY):
Code:
[I][SIZE="4"][CENTER][B]***** Check FAQ #5 before proceeding any further! *****[/B][/CENTER][/I][/SIZE]
Boot to bootloader by holding Volume Up and Power buttons.
Connect the phone to the computer via USB cable.
Go to your ADB folder (for me it is C:\Android\). Press “Shift” and click the right mouse button. Click on “Open command window here”.
In the console write “fastboot devices” to see if your computer recognizes your OnePlus 3.
When you could see that your device is recognized, write “fastboot flash recovery recovery_op3.img” to flash Stock Recovery of OxygenOS.
Disconnect the device, press volume up once, then press the power button once to turn off the phone.
Boot into recovery by holding Volume Down (-) and Power button down for a few of seconds.
Now, for some people, it will ask a password. If not, continue to #9 and ignore #8. If it asks you to enter a password to decrypt your data, choose “Forgot password” and let it erase all your data and let it reboot. (MAKE SURE YOU BACKED UP YOUR PERSONAL DATA BEFOREHAND). Most likely, it will reboot to the OS, so boot it to recovery again. Go to #10.
For those who doesn’t have to enter a password, press “English”. Press “Wipe data and cache” > “Erase everything (Music, pics, etc.)” > “This cannot be undone, continue?”. Moreover, let it wipe your data. Most likely, it will reboot to the OS, so boot it to recovery again. Go to #10.
Code:
[CENTER][I][SIZE="4"][B]AT THIS POINT IF YOU HAD DM-VERITY ERROR/ISSUE, IT SHOULD BE FIXED AND GONE.
IF IT STILL APPEARS, DON'T WORRY IT WILL BE GONE AFTER #12
IT CAME BACK TO ME ONE MORE TIME, BUT I GOT IT FIXED.
***** Check FAQ #6 for more information *****[/B][/I][/SIZE][/CENTER]
Select “English” > “Install from ADB” > “Ok”. Connect your phone to your computer. Go to your ADB folder (for me it is C:\Android\). Press “Shift” and click the right mouse button. Click on “Open command window here”.
In the console, write “adb devices” to see if your computer recognizes your OnePlus 3.
When you could see that your device is recognized, write “adb sideload OnePlus3Oxygen_16_OTA_041_all_1702081756_0f1e56a75f.zip”
to flash OxygenOS v4.0.3. (See FAQ #4 and #17 if you have issues)
Reboot and you have OxygenOS v4.0.3!
Sign-in into your Google account and Download the “DiskInfo” app from the Play Store. Launch it, and press “Data (userdata)”. You should see:
- Encrypted: yes
- Decrypted block device: /dev/block/dm-1
- Mount point: /data
- File system: f2fs
A. If you see that it is in F2FS file system format, proceed to Section C (FLASHING YOUR CUSTOM ROM) OR Section D (FLASHING AND ROOTING STOCK OOS OR UNROOT).
B. However, for some people (for some reason) it does not happen. You would see that your file system format (for userdata) is still on EXT4. Don’t be frustrated. A little bit more work needed to be done. Therefore, go to Section B (CHANGING FILE SYSTEM FORMAT AND ENCRYPTING OR DECRYPTING YOUR DEVICE). It will solve that problem.
Code:
[I][SIZE="4"]* Your phone needs to be encrypted by default. It comes like that from the
manufacturer. See the following links:
1. [url]https://forums.oneplus.net/threads/encrypted-oneplus-3.452572/page-2[/url]
2. [url]http://www.androidpolice.com/2015/10/19/android-6-0-will-finally-require-manufacturers-to-enable-full-disk-encryption-by-default-on-new-devices/[/url]
3. [url]http://arstechnica.com/gadgets/2015/10/android-6-0-re-implements-mandatory-device-encryption-for-new-devices/[/url]
4. [url]https://source.android.com/security/encryption/[/url]
5. [url]http://www.howtogeek.com/141953/how-to-encrypt-your-android-phone-and-why-you-might-want-to/[/url]
6. [url]http://www.extremetech.com/mobile/216560-android-6-0-marshmallow-makes-full-disk-encryption-mandatory-for-most-new-devices[/url]
[/I][/SIZE]
B - PROCEDURE (CHANGING FILE SYSTEM FORMAT AND ENCRYPTING OR DECRYPTING YOUR DEVICE):
Go to: Settings > Security & fingerprint > Encryption (located at the bottom). Make sure it says “Encrypt phone (Encrypted)”. To make sure
you will need to do a factory reset.
Now go to: Settings > Backup & reset > Factory data reset. In “Optional” select “Erase internal storage” and press “RESET PHONE”. Confirm by pressing “ERASE EVERYTHING”.
It will reboot to Stock Recovery and wipe your data. When it’s done, it will reboot to the OS.
Again, download the “DiskInfo” app from the Play Store. Launch it, press “Data (userdata)”. Now you should see (it wouldn’t show “Encrypted: yes” at all):
- Mount point: /data
- File system: f2fs
Now go to: Settings > Security & fingerprint > Encryption (located at the bottom). Make sure it says “Encrypt phone” and that you can press it. (DON’T ENCRYPT YOUR PHONE WITH THAT OPTION)
Now you successfully changed your file system to F2FS and decrypted your phone!
Code:
[I][SIZE="4"] * With Official TWRP v3.0.3-0 and modified TWRP v3.0.3-x v16 (from [user=3873953]@eng.stk[/user])
you are able to use the phone in encrypted mode, password request at
boot up and with Stock or rooted OOS v4.0.3 (Also, I tested it myself).
* Therefore, I will ask you to encrypt the phone back again. Proceed with
the following instructions:
[CENTER]***** Check FAQ #9 for more information *****[/CENTER][/I][/SIZE]
Reboot to Stock recovery v2.0
Select “English” > “Install from ADB” > “Ok”. Connect your phone to your computer. Go to your ADB folder (for me it is C:\Android\). Press “Shift” and click the right mouse button. Click on “Open command window here”.
In the console, write “adb devices” to see if your computer recognizes your OnePlus 3.
When you could see that your device is recognized, write “adb sideload OnePlus3Oxygen_16_OTA_041_all_1702081756_0f1e56a75f.zip”
to flash Oxygen OS v4.0.3. (See FAQ #4 and #17 if you have issues)
Reboot your device. Now you back to being encrypted and “userdata” was changed successfully to F2FS file format on Stock Oxygen OS v4.0.3!
Go to Section C (FLASHING YOUR CUSTOM ROM) to properly flash your custom ROM. *** IT’S YOUR CHOICE ***
OR Go to Section D (FLASHING AND ROOTING STOCK OOS OR UNROOT) to remain in stock, root or unroot. *** IT’S YOUR CHOICE ***
C - PROCEDURE (FLASHING YOUR CUSTOM ROM):
Boot to bootloader by holding Volume Up and Power buttons.
Connect the phone to the computer via USB cable.
Go to your ADB folder (for me it is C:\Android\). Press “Shift” and click the right mouse button. Click on “Open command window here”.
In the console write “fastboot devices” to see if your computer recognizes your OnePlus 3.
When you could see that your device is recognized, write “fastboot flash recovery twrp-3.0.4-1-oneplus3.img” to flash Official Unreleased TWRP v3.0.4-1.
Disconnect the device, press volume up once, then press the power button once to turn off the phone.
Boot into the TWRP by holding Volume Down (-) and Power button down for a few of seconds.
It takes a little bit more time to boot to blu_spark’s, Official and Unofficial TWRPs. Be patient.
Code:
[I][SIZE="4"] * The “PASSWORD UPON ENTERING TWRP” should not be an issue any longer (only
if you followed the whole guide). It is caused by the TWRP being modified
(has an issue with encryption), not being officially released and fully
supported for the Nougat update. Versions “.28”, “.22” and “.19” are known
for that issue. Therefore, DO NOT USE THEM. If one of them works for
you, then use it at your own risk.
[CENTER]***** Check FAQ #9 for more information *****
[/CENTER][/I][/SIZE]
Press “Wipe” > “Advanced Wipe”, and select “Dalvik / ART Cache”, “System”, “Data” and “Cache”. Then swipe “Swipe to Wipe” for a clean flash.
After it’s done, go back to the main menu. Press “Install” and look for your desired custom ROM and press on the zip file to install it.
* I used FreedomOS v2.3 as an example and I didn't have any battery drain issues. (For more information, see FAQ #10)
D - PROCEDURE (FLASHING AND ROOTING STOCK OOS OR UNROOT):
Code:
[I][SIZE="4"][COLOR="Red"][I] * If you don't have dm-verity issue, file system change issue or password
upon entering TWRP, then go to #1.
* If you came from having dm-verity issue, file system change issue or
password upon entering TWRP (solved by using Procedure A and/or B),
then go to #12.
[/I][/COLOR][/I][/SIZE]
Boot to bootloader by holding Volume Up and Power buttons.
Connect the phone to the computer via USB cable.
Go to your ADB folder (for me it is C:\Android\). Press “Shift” and click the right mouse button. Click on “Open command window here”.
In the console write “fastboot devices” to see if your computer recognizes your OnePlus 3.
When you could see that your device is recognized, write “fastboot flash recovery recovery_op3.img” to flash Stock Recovery of OxygenOS.
Disconnect the device, press volume up once, then press the power button once to turn off the phone.
Boot into recovery by holding Volume Down (-) and Power button down for a few of seconds.
Select “English” > “Install from ADB” > “Ok”. Connect your phone to your computer. Go to your ADB folder (for me it is C:\Android\). Press “Shift” and click the right mouse button. Click on “Open command window here”.
In the console, write “adb devices” to see if your computer recognizes your OnePlus 3.
When you could see that your device is recognized, write “adb sideload OnePlus3Oxygen_16_OTA_041_all_1702081756_0f1e56a75f.zip”
to flash OxygenOS v4.0.3. (See FAQ #4 and #17 if you have issues)
Reboot and you have OxygenOS v4.0.3!
A. UNROOT - At this point, if you want to unroot and go back to completely stock, then use this guide: https://forums.oneplus.net/threads/guide-how-to-unroot-your-oneplus-3-and-go-back-completely-to-stock.456232/
*** Most of the procedures for unrooting you have already done. Only locking bootloader is left. Good Luck! (YOU CAN STOP HERE)
B. ROOT - Continue to #13
Boot to bootloader by holding Volume Up and Power buttons.
Connect the phone to the computer via USB cable.
Go to your ADB folder (for me it is C:\Android\). Press “Shift” and click the right mouse button. Click on “Open command window here”.
In the console write “fastboot devices” to see if your computer recognizes your OnePlus 3.
When you could see that your device is recognized, write “fastboot flash recovery twrp-3.0.4-1-oneplus3.img” to flash Official Unreleased TWRP v3.0.4-1.
Disconnect the device, press volume up once, then press the power button once to turn off the phone.
Boot into the TWRP by holding Volume Down (-) and Power button down for a few of seconds.
It takes a little bit more time to boot to blu_spark’s, Official and Unofficial TWRPs. Be patient.
Connect you OnePlus 3 to your computer and copy the SuperSU v2.79 (Stable) to your device.
Pick up your phone. From the main menu, press “Install” and look for the SuperSU v2.79 (Stable zip file). Press it to install the root and after it's done, reboot to the OS.
That's it! Everything should be working properly
(except the bugs and issues on OxygenOS Nougat update).
ENJOY!
CREDITS:
@NevaX1 --------------> For FreedomOS ROM
@jamal2367 -----------> For ExperienceOS ROM
@cpt.macp ------------> For in depth dm-verity remover guide
@Adithya R -----------> For in depth file system formating from EXT4 to F2FS guide
@eng.stk --------------> For modified TWRP that supports F2FS file format
@LELBOT --------------> For in depth dm-verity remover and file system formating from EXT4 to F2FS guides
@Naman Bhalla ------> For in depth bootloader unlocking, flashing TWRP, rooting, nandroid backup guide
@calvinistmac --------> For providing an unroot for OnePlus 3 guide
@Nishidh --------------> For providing OxygenOS v4.0.3 and Beta 11 OTA download links
@jcadduono ----------> For providing Official TWRP
@dianlujitao ----------> For providing Unofficial TWRP and LineageOS 14.1 ROM
@th3g1z ---------------> For providing an easy solution for Dm-verity issue
--------------------------> OnePlus Community and XDA forums for providing with issues, solutions and requests
FAQ (Q&A):
Q: I can’t boot into TWRP! What to do?
A: Try using the previous TWRP or Stock Recovery.
[*]Q: I can’t boot into the OS! What to do?
A: Most likely some of the OS files are damaged or executed incorrectly. Try flashing or sideloading the OS again.
[*]Q: I can’t transfer files to my OP3 after wiping Internal storage OR Data folder/s in TWRP! What to do?
A: Don’t panic. Reboot to TWRP. It will create a folder so you can transfer files again.
[*]Q: I got an error sideloading the OS. Why is that?
A: Sometimes it occurs when the USB cable is wiggled side to side (the process stops at 92% with an error). Try again without touching
or moving the USB cable and the phone. Alternatively, it could be that USB debug is not enabled (not sure about that).
[*]Q: Is there an alternative way to get rid of dm-verity issue?
A: One simple command-line (enable) in bootloader can solve it. Check this post: https://forum.xda-developers.com/showpost.php?p=70698410&postcount=112
Otherwise, check this thread: https://forum.xda-developers.com/oneplus-3/how-to/fix-device-mapper-verity-simple-trick-t3530685 This guide uses the .28 twrp
(NOT RECOMMENDED, BUT USE TWRP FROM @eng.stk) to use Stock Recovery, which I think is a bit more complex.
OR: https://forum.xda-developers.com/showpost.php?p=70415499&postcount=33
My guide uses only bootloader, Stock Recovery and TWRP from @eng.stk. Either way, they are the same guides.
[*]Q: The "dm-verity issue" came back after flashing OTA of stock OOS v4.0.2 via the TWRP! What to do?
A: Simply follow "Section A" instructions until #13. After you sideloaded the OTA it will be gone. It happened the second time when I tried to
flash the OTA via TWRP. Therefore, don't flash OTA of stock OOS v4.x.x via TWRPs. Only via Stock Recovery v2.0
I got it fixed only after sideloading the OTA via Stock Recovery v2.0 (Check post #29 for more information)
If it still doesn't work check this thread and read it thoroughly: https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-t3539129
For more information, read FAQ #12
[*]Q: Your guide to change file format doesn’t work, OR I want to change “Cache” and “System” to F2FS as well. What to do?
A: Simply go to this link and at your own risk: https://forum.xda-developers.com/oneplus-one/general/guide-formatting-ext4-to-f2fs-losing-t3352116
Furthermore, @cpt.macp mentioed in post #34 in this thread that "/system and /cache need not to be f2fs . Oneplus Supports only /data
as f2fs and nothing else ."
[*]Q: I can’t log in into Snapchat after a clean flash of my desired custom ROM or after rooting my device. How to fix this?
A: I had the same issue, and it doesn’t occur to everybody. Before DIRTY flashing (wiping System, Cache and Dalvik only) the custom ROM
-OR- rooting your device, install Snapchat and log into it (on stock OOS v4.x.x). It might be a SuperSU (root) issue with Snapchat
(they enforced their security with rooted devices).
Also, OnePlus 3 has an issue with on-screen navigation bar. So, disable it in the "Buttons" menu until OnePlus fixes the glitch/bug.
[*]Q: Why did you choose TWRP v15 from @eng.stk -OR- Official TWRP v3.0.3-0 -OR- Unofficial TWRP v3.0.3-0?
A: They all work with the phone being encrypted, requesting a password on bootup to the OS and support F2FS file system.
.28 – had issues with encryption and F2FS file system, but for some users it works wonders.
.22 and .23 – I did not test, but I have read that .23 worked (decrypted).
.19 – Tested and solved the password issue, but had a mouse pointer in the middle of the TWRP (wasn’t a big deal). Worked in decrypted mode.
P.S. The official TWRP has issues with the name of the device. If you encounter those issues, then let the developer of the ROM
you're using know about it. So, he could fix it (it's a small fix). OR use TWRP v15 from @eng.stk. Unofficial TWRP is to be used
with LineageOS 14.1 & Experience v10 ROMs. Also, here is the reason why: https://forum.xda-developers.com/showpost.php?p=70593986&postcount=53
Also, Official TWRP v3.0.2-1 doesn't support Nougat. Therefore, you won't be able to boot to this TWRP. Don't use it for Nougat.
[*]Q: I am experiencing a battery drain. Why?
A: Facebook was the main issue for that, but it is now fixed (some users said that it still exists). I use Freedom OS v2.2 and no
issues so far with the battery. I got 5 hours SOT (Screen On Time) with 45% left (on the first day), and 5½ hours SOT with 26%
battery left (on the second day). Now, I think the OS is balanced because I get almost 8 hours of SOT. Try looking for a solution
in the forums. Also, disable mobile data when using WIFI and vise versa. Furthermore, battery life may vary with the applications
you use on a daily basis, screen brightness, how much and long you touch the screen, etc. (See the attached thumbnails)
[*]Q: I am experiencing issues with the Play Store app (It’s stuck on downloading). Is there a fix?
A: When you first launch it, it tries to update itself. It will crash 1-2 times. After that, everything works just fine. Also, uninstall or don’t
install Truecaller app (well known to cause this issue). It was fixed in OOS v4.0.2, but some users still experience this issue.
In addition, if nothing works, then try uninstalling the Play Store app and reinstall it via OpenGApps. For those who are not rooted,
try finding the Play Store app via the web (install it under your own risk, as I'm not responsible for the damages).
[*]Q: Why do you use stock recovery to sideload the OS?
A: First of all, you’re going to sideload OTA of Oxygen OS, which you can’t flash in the TWRP (some people can and you might get dm-verity
issue). Secondly, the stock recovery is simple and easy to use. Thirdly, If you flash the OTA from the official TWRP, you will get a dm-verity
message. Besides, OnePlus provided only with "OTA" zips and not "signed flashable" zips.
THE DM-VERITY ISSUE (CHECK THE FOLLOWING SOURCES FOR MORE INFORMATION):
https://www.xda-developers.com/qualcomm-maintains-its-dedication-to-security-with-secure-boot/ ; https://www.xda-developers.com/stri...r-correction-to-come-with-android-7-0-nougat/ ;
https://source.android.com/security/verifiedboot/ ; https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-t3539129 ;
https://forum.xda-developers.com/showpost.php?p=70574596&postcount=34 ; https://forum.xda-developers.com/showpost.php?p=70622726&postcount=97 ;
https://forum.xda-developers.com/showpost.php?p=70622760&postcount=98 ; https://forum.xda-developers.com/showpost.php?p=70622849&postcount=102 ;
https://forum.xda-developers.com/showpost.php?p=70622999&postcount=104
[*]Q: What if I want to go back using Oxygen OS v3.2.8 (Andriod v6.0.1) or custom ROMs based on it?
A: Simply instead of using Stock Oxygen OS v4.0.2 OTA in this guide, use Stock Oxygen OS v3.2.8 OTA.
It will bring back EXT4 file system and you can use Xposed.
[*]Q: After clean flashing my Custom ROM in TWRP, I get the following message: "No OS Installed. You Sure You Want
To Reboot". What to do?
A: Try dirty flashing your Custom ROM. (Source: https://forum.xda-developers.com/showpost.php?p=70622460&postcount=5291)
[*]Q: Android System WebView is disabled in the Play Store. When I try to enable it, it won't do anything. Unless I tap
it rapidly and it's still in disabled mode. What to do?
A: No need to worry here. It is normal due to Chrome being the new WebView in Android Nougat.
(Sources: http://www.androidpolice.com/2016/07/20/google-explains-chrome-will-become-webview-android-7-0/ AND https://productforums.google.com/forum/#!topic/nexus/Ni35XW6eRR0
https://www.reddit.com/r/GooglePixel/comments/5ayh5d/android_system_webview_not_enabled/ AND https://www.reddit.com/r/Nexus6P/comments/57t1hw/android_system_webview_keeps_disabling/)
[*]Q: Should I flash a custom Kernel (ElementalX or Blu_spark) on a custom ROM?
A: You can, but you might have CPUs being on max load and overheating issues (it's not caused by the kernel itself).
They work best, and only, if you have stock OOS v4.0.2 installed and rooted with SuperSU v2.79 Stable. Yes, for some
users the custom kernels work. But, for some they won't, due to firmware issues. You can try them on your Custom
ROM, but it's not guaranteed to work. The developers of FreedomOS and ExperienceOS solved this issue.
**Some users found a solution by setting SELinux to Permissive mode instead of Enforced.
I do not recommend setting your SELinux in Permissive mode! (as well as the developer of ElementalX)!
For more information, check this thread: https://forum.xda-developers.com/oneplus-3/how-to/potential-fix-cpu-battery-drain-aosp-t3543369
Also, check these articles: https://www.xda-developers.com/onep...ng-of-selinux-to-permissive-mode-in-fastboot/ ; https://www.xda-developers.com/onep...lus-33t-bootloader-vulnerability-in-next-ota/
[*]Q: I'm getting the error (cannot read "image.zip") when trying to sideload Stock OOS. Why and how to fix this?
A: For some reason, the thread added a space in the OOS file name. If you copy the file name for Stock OOS v4.0.2 from this thread,
make sure it doesn't have spaces in it (-OR- in any other file -OR- in the console).
** Also, make sure to enable USB Debugging in Developer Options.
** Follow these guidelines separately (if the first one doesn't work, use the second or third guideline):
Reinstall OnePlus Drivers using the attached zip (OnePlus_USB_Drivers_Setup.zip) and try again. In addition,
make sure your file name is not ending with ".zip.zip" or written like that in the console.
Bootup to your OS and connect the phone to the computer (make sure to choose transfer files mode).
Copy Stock OOS v4.0.2 OTA zip to the device and reboot to recovery. Select "Install from Internal Storage",
look for the OTA file and install it.
Read the following threads/posts/articles: https://forum.xda-developers.com/showthread.php?t=1990405&page=2 ;
http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/ ; https://forums.oneplus.net/threads/cannot-read-ota-zip.457965/ ;
https://www.reddit.com/r/oneplus/comments/504qgv/adb_cannot_read_error/ ; https://www.androidexplained.com/fix-cannot-read-sideload-update/ ;
https://forum.xda-developers.com/android/general/guide-how-to-adb-to-push-pull-files-t3372710
[*]Q: Every second song in Google Play Music gets skipped. What to do?
A: Make sure to disable AdAway, then reboot the device. Everything should come back to normal.
P.S. I will add more questions and answers if they get repeated in the forums, or the issue can be solved.
Updates & News:Updates:
January 14th, 2017 ---> Reverted modified TWRP v3.0.3-x v12 from @eng.stk back to v3.0.2-0 v11
(Reason: https://forum.xda-developers.com/showpost.php?p=70556176&postcount=2540)
January 15th, 2017 ---> Added an introduction section; Modified sections A, B and C for more fluent and easier guidelines; Added one more Q&A
January 20th, 2017 ---> Added Section D (FLASHING AND ROOTING STOCK OOS OR UNROOT) ; Modified sections A, B and C ; Modified FAQ (Q&A)
and added more Q&A ; Updated to OOS v4.0.2, Beta 11, Official TWRP v3.0.3-0, Unofficial TWRP v3.0.3-0, Modified TWRP v14 from blu_spark ;
Modified Intoduction, "Disclaimer & Inportant" and "What will you need?" sections.
January 23rd, 2017 ---> Updated to latest Modified TWRP v3.0.3-x blu_spark v15 from @eng.stk
January 25th, 2017 ---> Added Unreleased Official TWRP v3.0.4-1 for Nougat ; Minor updates to the guide and FAQ.
February 9th, 2017 ---> Added and updated the thread with OxygenOS v4.0.3 ; Added one more FAQ and a new story
February 10th, 2017 ---> Updated to latest Modified TWRP v3.0.3-x blu_spark v16 from @eng.stk
News:
January 14th, 2017 ---> Oxygen OS v4.0.2 coming next week! Confirmed.
(Sources: https://forums.oneplus.net/threads/4-0-2-in-works-roll-out-by-next-week-confirmed.488348/ AND https://twitter.com/OnePlus_ITA/status/819200734067617792 AND
http://www.androidsage.com/2017/01/14/oneplus-3-and-3t-oxygen-os-4-0-2/)
January 15th, 2017 ---> We as a community of developers and users, urge OnePlus to release kernel sources by complying with GPLv2.
(Source: https://www.xda-developers.com/xda-developers-urges-oneplus-to-comply-with-gplv2-and-release-kernel-sources/)
January 18th, 2017 ---> OnePlus said that OxygenOS 4.0 doesn’t use a Debug Kernel
(Source: https://www.xda-developers.com/oneplus-oxygenos-4-0-doesnt-use-a-debug-kernel/)
January 20th, 2017 ---> Seems like OnePlus released Kernel Sources for OnePlus 3/3T. Finally!
(Sources: https://www.xda-developers.com/oneplus-releases-android-nougat-kernel-sources-for-the-oneplus-33t/ AND https://github.com/OnePlusOSS/android_vendor_qcom_thulium/commits/oneplus/QC8996_N)
January 20th, 2017 ---> The Best ROMs, Kernels, and Mods for the OnePlus 3
(Source: https://www.xda-developers.com/oneplus-3-best-stuff/)
January 21st, 2017 ---> Remap your phone’s hardware buttons with "Button Mapper" app
(Source: https://www.xda-developers.com/xda-...an-app-to-remap-your-phones-hardware-buttons/)
January 21st, 2017 ---> How to move Chrome’s address bar to the bottom without a visual bug?
(Source: https://www.xda-developers.com/psa-...ar-to-the-bottom-no-longer-causes-visual-bug/)
January 22nd, 2017 ---> Enable this Chrome Flag to Lock Rotation in Fullscreen Videos
(Source: https://www.xda-developers.com/enable-this-chrome-flag-to-lock-rotation-in-fullscreen-videos/)
January 22nd, 2017 ---> Deeply Integrated Progressive Web Apps (WebAPKs) are Live for Chrome on Android
(Source: https://www.xda-developers.com/deep...-apps-are-already-live-for-chrome-on-android/)
January 25th, 2017 ---> Open Betas updates are paused for a month for OnePlus 3/3T due to Chinese New Year
(Source: https://forums.oneplus.net/threads/...s-3-and-3t-will-be-paused-for-a-month.492623/)
January 25th, 2017 ---> Security Analysts Identify a Trojan that Quietly Purchase Apps, a Rootkit that takes over your Device,
and Ransomware that Locks your Device
(Source: https://www.xda-developers.com/secu...device-and-ransomware-that-locks-your-device/)
January 28th, 2017 ---> An update from @rovo89 about developing Xposed for Nougat
(Source: https://forum.xda-developers.com/showpost.php?p=70773752&postcount=41)
February 1st, 2017 ---> OnePlus got caught red-handed in Benchmark cheating and came clean
(Sources: https://www.xda-developers.com/benc...ght-red-handed-and-what-theyve-done-about-it/ ; http://www.androidauthority.com/oneplus-meizu-just-got-busted-benchmark-cheating-746640/)
February 9th, 2017 ---> Two Critical OnePlus 3/3T Bootloader Security Flaws Discovered, One Patched and Other being Addressed
(Source: https://www.xda-developers.com/two-...overed-one-patched-and-other-being-addressed/)
Very easy to follow guide. I ended up at B8 "Now you successfully changed your file system to F2FS and decrypted your phone!". I would like my phone to be encrypted, but if I do it through the OS, TWRP does not accept my password for the data partition?
Thanks so much, mate. This is a really good job which is gong to help to many people
Hi,
thanks :good:
For info: new twrp-3.0.3-x_blu_spark_v12-op3 is out
source: https://forum.xda-developers.com/showpost.php?p=70541197&postcount=2519
@+
Hi, i have oxygen os 4.0.1 rooted and twrp v11 bluspark...But its normal when i deletet some file i dont see immeditely the free space unti i reboot the phone...this happened sometimes and sometimes not...Its a bug?
I have flash as you post, when flash done i check file system by diskinfo, it displayed "userdata not mounted". how do i fix it. plz help me. thank you very much.
Lol this is just what I did:
1. Flash latest @eng.stk TWRP, swipe to allow modifications
2. Wipe system, data, cache
3. Install 1.4GB 4.0.1 zip
4. Wipe dalvik and cache
5. On Mount, check Mount /system as read-only
6. Reboot to system
You now have stock 4.0.1 system, kernel, and recovery.
7. Boot to recovery. TWRP is overwritten by the OOS 4.0.1 recovery.
8. Wipe everything. /data is now f2fs
Optional: flash TWRP, swipe to allow modifications, and do not check Mount /system as read-only to keep it.
No issues at all.
Sent from my OnePlus 3 using XDA Labs
Thank you! Solved my problem with Dm-Verity. Do you think, for the future *4.0.2* update or whatever number will be, that we will be able to flash OTA via TWRP or we'll need stock recovery? Only full zip with TWRP?
You might want to change that TWRP v12 back to v11. Eng.stk found some issues with v12 and pulled it.
And great guide BTW ?
Sent from my OnePlus 3 using Tapatalk
Greetings ?,
After reading this guide i just need to ask several thinks to make clear.
Recently my brothers give me his op3 as he changes to op3t ; . I want to change the phone font and afaik its to impossible to do so without root.
Im currently on 4.0 ; will this guide applicable on my phone ? Or is there a way to change font without root. Thanks in advance
laupuy said:
Hi,
thanks :good:
For info: new twrp-3.0.3-x_blu_spark_v12-op3 is out
source: https://forum.xda-developers.com/showpost.php?p=70541197&postcount=2519
@+
Click to expand...
Click to collapse
I cant't download it from that thread v12 - says file might have been deleted.
mit2nil said:
I cant't download it from that thread v12 - says file might have been deleted.
Click to expand...
Click to collapse
Go to the thread's Downloads tab, download the first file. Ugh it was just mentioned above that v12 was removed.
Sent from my Lenovo A3300 using XDA Labs
VincentJoshuaET said:
Go to the thread's Downloads tab, download the first file. Ugh it was just mentioned above that v12 was removed.
Sent from my Lenovo A3300 using XDA Labs
Click to expand...
Click to collapse
Yup my bad. I was on first page and just used reply button. Never mind.
Answers to your concerns:
I apologize for the late response. I was doing a bit of research to answer all of your questions.
Thank you for your patience!
jackiass said:
Very easy to follow guide. I ended up at B8 "Now you successfully changed your file system to F2FS and decrypted your phone!". I would like my phone to be encrypted, but if I do it through the OS, TWRP does not accept my password for the data partition?
Click to expand...
Click to collapse
Seems like "sideload"ing OOS v4.0.1 didn't change your file system, correct?
I would recommend to start over. When you are done B7, "sideload" OOS v4.0.1 to encrypt the device again. After that's done, continue to section C.
Crazyhat said:
Thanks so much, mate. This is a really good job which is gong to help to many people
Click to expand...
Click to collapse
You're welcome!
Thank you!
I tried very hard on gathering the right information and doing the testing on my OP3.
I almost got it bricked because of OOS v4.0.0, so I decided to post an easy to follow guide.
laupuy said:
Hi,
thanks :good:
For info: new twrp-3.0.3-x_blu_spark_v12-op3 is out
source: https://forum.xda-developers.com/showpost.php?p=70541197&postcount=2519
@+
Click to expand...
Click to collapse
Thank you very much! I have updated the thread.
UPDATE: Reverted back to v11 due to data corruption issues.
playerboys10 said:
Hi, i have oxygen os 4.0.1 rooted and twrp v11 bluspark...But its normal when i deletet some file i dont see immeditely the free space unti i reboot the phone...this happened sometimes and sometimes not...Its a bug?
Click to expand...
Click to collapse
I think it's not normal and you should see an immediate change in your free space.
I couldn't find any information about that.
Your best options are to follow this guide (if you didn't already) AND/OR post this issue in OnePlus 3 community forums.
yohan_xda said:
I have flash as you post, when flash done i check file system by diskinfo, it displayed "userdata not mounted". how do i fix it. plz help me. thank you very much.
Click to expand...
Click to collapse
Did you "sideload" stock OOS in stock recovery OR flash custom ROM via TWRP (I think this one)?
Also, where did you stop (section and number)?
VincentJoshuaET said:
Lol this is just what I did:
1. Flash latest @eng.stk TWRP, swipe to allow modifications
2. Wipe system, data, cache
3. Install 1.4GB 4.0.1 zip
4. Wipe dalvik and cache
5. On Mount, check Mount /system as read-only
6. Reboot to system
You now have stock 4.0.1 system, kernel, and recovery.
7. Boot to recovery. TWRP is overwritten by the OOS 4.0.1 recovery.
8. Wipe everything. /data is now f2fs
Optional: flash TWRP, swipe to allow modifications, and do not check Mount /system as read-only to keep it.
No issues at all.
Sent from my OnePlus 3 using XDA Labs
Click to expand...
Click to collapse
Yes, that might be the easy way when you have no issues. But, this guide deals with common issues (dm-verity, twrp password etc.) users face when they tried to update to OOS v4.0.x
If you'll face these issues in the future, you'll know where to find the related guide to fix them.
Hurizen said:
Thank you! Solved my problem with Dm-Verity. Do you think, for the future *4.0.2* update or whatever number will be, that we will be able to flash OTA via TWRP or we'll need stock recovery? Only full zip with TWRP?
Click to expand...
Click to collapse
You are very welcome!
You could flash OTA via TWRP (full size zip and not the small 40mb zip), but I'm afraid that it might "break your root" (you wouldn't have it anymore). It can be fixed by flashing SuperSU.
Technically, you could dirty flash (wipe System, Cache and Dalvik only) the new OTA. If you would have issues after dirty flashing, post your bugs/issues, and most likely you would have to clean flash the OTA.
Give it a try (backup your personal data and dirty flash) or wait for user feedback on the new OTA.
VincentJoshuaET said:
Go to the thread's Downloads tab, download the first file. Ugh it was just mentioned above that v12 was removed.
Sent from my Lenovo A3300 using XDA Labs
Click to expand...
Click to collapse
Thank you for replying back to him! I appriciate it!
mit2nil said:
I cant't download it from that thread v12 - says file might have been deleted.
Click to expand...
Click to collapse
I appologize about that. I have updated the thread.
Explorer23 said:
You might want to change that TWRP v12 back to v11. Eng.stk found some issues with v12 and pulled it.
And great guide BTW
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
With a bit of delay, I've put back the link to v11.
Thank you, and I hope it helped you!
dinesh7208 said:
Greetings ,
After reading this guide i just need to ask several thinks to make clear.
Recently my brothers give me his op3 as he changes to op3t ; . I want to change the phone font and afaik its to impossible to do so without root.
Im currently on 4.0 ; will this guide applicable on my phone ? Or is there a way to change font without root. Thanks in advance
Click to expand...
Click to collapse
Personally, I don't mess around with fonts. But, this guide will be applicable for rooting your phone.
Check the following threads for the fonts: https://forum.xda-developers.com/oneplus-3/help/change-font-t3426785
https://forum.xda-developers.com/oneplus-3/help/how-to-change-font-one-plus-3-t3434351
https://forum.xda-developers.com/android/themes/fonts-flashable-zips-t3219827
https://forum.xda-developers.com/oneplus-3/help/cb7-custom-fonts-t3509759
I hope they help.
I wish I had found this guide before but never mind. I was following original rooting guide by Naman on my OP3 running stock OOS 4.0.1. I used twrp v28 of blue spark and as observed by many I ended up in encryption issues and couldn't take nandroid backup so I didn't proceed.
Now, it seems it has been fixed with latest twrp (v11) by blue spark. My /data partition is already f2fs and cache is /ext4.
What steps should I follow to get back correct recovery and hopefully root as well? I am hoping that I do not need to sideload 4.0.1.
mit2nil said:
I wish I had found this guide before but never mind. I was following original rooting guide by Naman on my OP3 running stock OOS 4.0.1. I used twrp v28 of blue spark and as observed by many I ended up in encryption issues and couldn't take nandroid backup so I didn't proceed.
Now, it seems it has been fixed with latest twrp (v11) by blue spark. My /data partition is already f2fs and cache is /ext4.
What steps should I follow to get back correct recovery and hopefully root as well? I am hoping that I do not need to sideload 4.0.1.
Click to expand...
Click to collapse
I've had all of the issues in this guide. So, I decided to post one because nobody posted in-depth guide to deal with OOS v4.0.1
Also, TWRP v28 has issues with encryption being on and F2FS issues too. It caused all of my problems. I was a bit lucky to find TWRP v19 (had a mouse pointer in the middle of the TWRP, no big deal). It worked with EXT4 and F2FS file systems but wasn't perfect due to working only in decrypted mode.
It seems like you don't have any issues. Am I correct? (No password request in TWRP, dm-verity message)
If you don't, go to section "C - PROCEDURE (FLASHING YOUR CUSTOM ROM)".
About file system - leave it be. Only "/data" should be F2FS, "/Cache" and "/System" as EXT4. To much work to change them to F2FS and TWRP formats them to EXT4 when you wipe them.
dbabaev21 said:
I've had all of the issues in this guide. So, I decided to post one because nobody posted in-depth guide to deal with OOS v4.0.1
Also, TWRP v28 has issues with encryption being on and F2FS issues too. It caused all of my problems. I was a bit lucky to find TWRP v19 (had a mouse pointer in the middle of the TWRP, no big deal). It worked with EXT4 and F2FS file systems but wasn't perfect due to working only in decrypted mode.
It seems like you don't have any issues. Am I correct? (No password request in TWRP, dm-verity message)
If you don't, go to section "C - PROCEDURE (FLASHING YOUR CUSTOM ROM)".
About file system - leave it be. Only "/data" should be F2FS, "/Cache" and "/System" as EXT4. To much work to change them to F2FS and TWRP formats them to EXT4 when you wipe them.
Click to expand...
Click to collapse
I do have both issues DM verity message as well as encryption issue. I just stopped doing any further changes and decided to keep using phone as it after I hit password encryption issue with TWRP as I couldn't take nandroid backup.
mit2nil said:
I do have both issues DM verity message as well as encryption issue. I just stopped doing any further changes and decided to keep using phone as it after I hit password encryption issue with TWRP as I couldn't take nandroid backup.
Click to expand...
Click to collapse
Then start from the beginning.
I was scared to death that I bricked my phone, but managed to get out quickly.
This version of TWRP works on both the TB-X605F (wifi) and TB-X605L (LTE). It does not work for the TB-X605FC/FL (Tab M10 FHD Rel).
Warning: this TWRP is for the Lenovo Smart Tab M10 with the Snapdragon 450 (SDA450) chipset. This image will not work for the second gen M10 (TB-X606F/L), which use a Mediatek SOC. See this thread.
For the M10 HD (TB-X505F/L), see this thread. For the TB-X505X, see this thread.
Code:
#include <std_disclaimer.h>
/*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Possible issues with TB-X605L
If the latest version of TWRP for TB-X605F doesn't work for your TB-X605L model, try version 3.4.0-0 from twrp.me.
Installation
TWRP for this device is officially supported. You can download it from twrp.me or in the TWRP App (from the PlayStore). Installation instructions are included on twrp.me.
It is recommended that you also install Magisk. This will ensure TWRP remains your default recovery.
Step-by-step guide
download TWRP to your PC (see the Download section below)
download magisk.zip to your MicroSD or OTG device. Get the latest Magisk zip file here.
if your bootloader is already unlocked, go to step 4. To unlock bootloader:
on tablet: go to Settings->System->About and press "Build number" 7 times to enable Developer Options.
on tablet: go to Settings->System->DeveloperOptions. Turn on: "OEM unlocking" and "USB debugging".
connect tablet to your computer. Tablet will ask for permission to "Allow USB debugging". Tick "always allow" and select "OK".
backup any files you want to keep to an external device (MicroSD/OTG/computer), because the next step will wipe all your photos, files, google account etc on the tablet.
Now unlock the bootloader:
Code:
adb reboot bootloader
fastboot oem unlock-go
fastboot reboot
flash the twrp image:
Code:
adb reboot bootloader
fastboot flash recovery twrp.img
if you haven't loaded Magisk yet, go to step 6. If you have already loaded Magisk, you can just reboot and you're finished:
Code:
fastboot reboot
adb reboot recovery
load Magisk (step one): reboot to recovery. Do not reboot into the system, because it will over-write TWRP with stock recovery. If that happens, go back to step 4 and start again. When you issue the reboot command (below), you have to immediately press the button combination to reboot to recovery (TWRP). Here are the steps:
issue the reboot command:
Code:
fastboot reboot
immediately press and hold all three buttons (Pwr+VolUp+VolDown). The tablet might reboot twice. Release all the buttons when you see the TWRP screen, or hear your PC acknowledge that ADB is connected.
load Magisk (step two): flash Magisk. In TWRP:
select "Install"
use "select storage" to locate device you stored magisk.zip on.
press the OK button
select the Magisk zip file
swipe to confirm Flash
when Magisk is finished, hit the back button to go back to main TWRP screen.
select "Reboot" then "System"
if the Magisk Manager app wasn't automatically loaded, you can get it here.
finished!
If you prefer to use button combos, rather than fastboot/ADB commands:
Vol Down + Power = fastboot mode
Vol Up + Vol Down + Power = recovery mode
Changelog
Code:
02/03/2022 - TWRP 3.6.1_9: new TWRP release
23/11/2021 - TWRP 3.6.0_9: new TWRP release
01/01/2021 - TWRP 3.5.0-0: new TWRP release
21/11/2020 - TWRP 3.4.0-1: new official version with SPL patch
19/11/2020 - promoted security patch level to 2099-12-31. No need to worry about SPLs ever again.
02/09/2020 - promote security patch level to 2020-08-01 for TB-X605F_S210208_200807_ROW
06/08/2020 - officially supported
31/07/2020 - upgrade to TWRP 3.4.0-0
- data decryption working (security patch 2020-04-01)
- landscape mode (by popular demand)
- add more partitions to Backup options
15/01/2020 - reverted to API 28 (Android Pie)
- renamed "sdcard1" to "external_sd"
- changed [ro.build.incremental.version] in preparation for OTA #4
24/11/2019 - fixed date/time & EDL reboot mode
- dropped back to API 27
20/11/2019 - initial commit (API 28) - encryption/decryption not working
Downloads
official
TWRP for X605F: twrp.me
Source code
github.com/minimal-manifest-twrp/platform_manifest_twrp_omni/tree/twrp-9.0
github.com/TeamWin/android_device_lenovo_X605F (official)
github.com/Yahoo-Mike/recovery_device_lenovo_X605F (unofficial)
FAQ
See the third post for answers to some FAQs like:
Will this TWRP work with other M10 and P10 devices?
Why is my "Data" partition empty (0 MB)?
how do I root my device?
Credits
The guys at TeamWin Recovery Project.
Everyone whose device trees I plagiarised from GitHub.
The amazing work of @Chaser42, @Long_Sam and others to get this project started.
XDA:DevDB Information
X605F Recovery, Tool/Utility for the Lenovo Thinkpad Tablet
Contributors
Yahoo Mike, Chaser42
Source Code: https://github.com/TeamWin/android_device_lenovo_X605F
Version Information
Status: Testing
Created 2019-11-19
Last Updated 2022-05-22 (v3.6.1 and warning for TB-X605L)
Encryption/Decryption
When you load the stock ROM, it creates and automatically encrypts the data partition. If you are not using the correct TWRP version, the data partition might be empty (0 MB). This is because TWRP failed to decrypt the data partition.
If your data partition is 0MB in TWRP, make sure you have loaded the latest version of TWRP (Nov 2020 or newer). Older builds required the security patch levels to match on TWRP and your system.
If you want to remove encryption completely, then you can use the dm-verity-forceencrypt tool. @turboperson123 has put together some instructions to remove encryption. If you've already loaded TWRP, then you only need to follow steps 6 and 7 from that post. @turboperson123 's method uses @Zackptg5 's Universal DM-Verity, ForceEncrypt, Disk Quota Disablers tool to remove encryption and dm-verity.
FAQs
Can I use this TWRP on other M10 and P10 tablets?
There are quite a few variants of these Tabs that use the Snapdragon 450 (SDM450) chipset:
TB-X605F (Tab M10 wifi) - tested working this TWRP
TB-X605L (Tab M10 LTE) - tested working with TWRP ( thanks @alexupsa )
TB-X705F/L (Tab P10) - no. Use the twrp available on this thread.
For the TB-X505F/L (M10 HD) see this post.
NOTE: the TB-606F/L (M10 2nd gen), TB-X605FC (M10 FHD) use different chipsets, so this TWRP won't work.
Why is my "Data" partition 0MB?
See the second post in this thread.
What should I backup?
Short answer: everything.
But the bare minimum might include:
System Image
Vendor Image
Firmware/Modem
Persist
Data
Cache
Boot
How do I root my device?
To root your device, here are the instructions for the:
X705F (thanks to @Chaser42)
X605F/L - follow steps 6 & 7 in the OP above. If you don't want to load TWRP, then try something like @Long_Sam's patched boot.img method.
X505F/L - follow the "step by step guide" in the OP above. Just make sure you use twrp for X505F (not for X605F).
How do I load OTAs with TWRP?
Note: if you ran the dm-verity-forceencrypt tool to unencrypt your /data, then the steps below will not work.
select "uninstall" in the Magisk Manager app. If MM doesn't reboot the system, then reboot - this will re-install stock recovery.
install the OTA (either in the system or using stock recovery).
re-flash TWRP (for the new security patch level)
re-install Magisk
TB-X605L working properly. Thank you!
TB-X605L working properly. Thank you!
Yahoo Mike said:
This is a work in progress. Volunteer testers are very welcome.
Click to expand...
Click to collapse
Wow...
That's really huge...
As we say here : "Monsieur, chapeau bas !"
Long_Sam
Lenovo has released quite a few variants of the Tab M10 now. I'm not sure this TWRP will work on all of them.
There are now even variants of a variant !
Code:
[B]M10[/B] with SDM-450 models: X605F (wifi) & X605L (LTE)
[B]M10 HD[/B] with SDM-429 models: X505F (wifi), X505L (LTE) & X505X (LTE Bands 1,2,3,4,5,7,8,20,38,40)
[B]M10 FHD[/B] with SDM-450 models: X605FC (wifi) & X605LC (LTE)
The M10 I have is shipped with a Snapdragon 450 (SDM-450) chipset & Hardware Code 63. But I see on their US site that Lenovo are now putting the SDM-429 in the X605. This might cause a problem with TWRP. I'm not sure if the kernels will be compatible.
The TWRP I've posted is for the X605F/L SDM450 (HW=63). I might need to compile a different TWRP for the SDM429 versions of the X605 & the X505.
If your X605 or X505 shipped with the SDM429, can you let me know if this TWRP works ? I need to know the Hardware Version, CPU and Hardware Code. Hardware Version and CPU are in System->About. The Hardware Code is in brackets after the S/N on the sticker on the back of the tablet, eg S/N Hxxxxxxx (63).
If you have an X605FC/LC, let me know if this TWRP works. I think it will, but I want make sure.
I have one with the 429 TB-X505F SD429 HW71 If i get some time today I might be bale to try it. I'll post soon as I do.
This morning I successfully compiled and ran the P10 kernel source on my M10. I had to tweak the config a bit. I tested it in TWRP. No problems.
Tomorrow, I'll inject it into the boot.img of the system ROM and see what happens. If it is mostly stable, then we're on the way to LOS for the M10. If it's completely stable, I'll push the source up to github.
I'll continue to use the stock kernel for the released versions of TWRP in this thread, though.
Thanks to @clsA for helping me work out that the M10 kernel is a subset of the P10 kernel.
@Yahoo Mike
thx for the twrp
succesfully flashed on my X605L
"Stock recovery image (recovery_stockROM.img) from TB-X605F_USR_S200065_1905280020_Q00332_ROW - just in case something goes wrong & you need to restore stock recovery. Only use this image on a TB-X605F. If you need it for any other variant, just ask in this thread and we'll track it down for you."
do you have the stock recovery for the X605L ?
how can i backup "DATA" inside twrp ?
will this help ?
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
OSIRIS2010 said:
...
do you have the stock recovery for the X605L ?
Click to expand...
Click to collapse
Now I think of it, you don't need it. If TWRP fails to flash, then stock recovery will still be there. If stock recovery is still not loading, just boot into the system and shutdown. When you shutdown, the system will re-flash stock recovery for you.
OSIRIS2010 said:
...
how can i backup "DATA" inside twrp ?
Click to expand...
Click to collapse
Have a look at the second post.
TL;DR...the dm-verity-forceencrypt tool will do it. But it will break the next OTA. The unencrypted P10 guys are having problems at the moment with this.
I've tried to get TWRP to unencrypt the data partition, but I can't get KeyMaster to initialise successfully. Maybe the next version of TWRP will be able to do it.
Yooo. Sorry I took so long works been crazy. I cant get it to reboot into twrp recovery. Its flashes the 605 recovery then I follow the next steps in the guide but I can only get it to reboot to the stock recovery screen. Run the reboot recovery command then immediately hold the volume + - down along with power. I tried a lot I let reboot twice then let off, and nothing then I tried several more times. Reflashing then the next step. I must not be holding my mouth...err I mean pushing the buttons right or the recovery just isn't gonna work. Add I'm very newbie at rooting and customizing. I've I've rooted one phone. A 70$ moto g5 plus I got off Ebay that was basically brand new. Installed twrp recovery and magisk. I bought that cause I have SD note 9 I cant root and have this need to play YouTube videos in my truck lol. Let me know if you have any suggestions I can try. Or ideas that might make it work. I pretty much fubard the tab and (at a different time) before I tried this recovery and was able to reflash stock img though odin.
11mackey11 said:
Yooo. Sorry I took so long works been crazy. I cant get it to reboot into twrp recovery. Its flashes the 605 recovery then I follow the next steps in the guide but I can only get it to reboot to the stock recovery screen. Run the reboot recovery command then immediately hold the volume + - down along with power. I tried a lot I let reboot twice then let off, and nothing then I tried several more times. Reflashing then the next step. I must not be holding my mouth...err I mean pushing the buttons right or the recovery just isn't gonna work. Add I'm very newbie at rooting and customizing. ...
Click to expand...
Click to collapse
Don't be too hard on yourself...you've done well to get this far.
I just had a quick look at the kernel for the X505F. It's very different from the X605F. So this TWRP definitely won't work for you. Sorry.
If you want me to build a TWRP for the X505F, PM me and we'll work something out.
How do you remove twrp I think that or magisk is giving me the booting issues. Half the time I reboot for things it gets stuck. Not sure if it's root or twrp but I can't seem to remove either.
cbomb1337 said:
How do you remove twrp I think that or magisk is giving me the booting issues. Half the time I reboot for things it gets stuck. Not sure if it's root or twrp but I can't seem to remove either.
Click to expand...
Click to collapse
If you uninstall Magisk, then the system will overwrite TWRP with stock recovery the next time you reboot. Just tap "uninstall" in the Magisk Manager app. You can also remove Magisk from TWRP following these instructions.
What kind of boot issues are you having? Are you using a TB-X605F with SDA450? Or is it something similar?
I am using Tb 605f it seems to be booting fine now after removing this riru module and edxposed. I'll just leave that and stick with just viper 4 Android lol
Do you know if them modules for increasing speed work? I think one of them was called fde and there the doze one.
cbomb1337 said:
I am using Tb 605f it seems to be booting fine now after removing this riru module and edxposed. I'll just leave that and stick with just viper 4 Android lol
Do you know if them modules for increasing speed work? I think one of them was called fde and there the doze one.
Click to expand...
Click to collapse
Good to hear it's all working again.
Sorry, I haven't tried any of those tweaks.
Lenovo have updated the stock ROM they serve for the TB-X605F through LMSA rescue. It's now at TB-X605F_USR_S210126_1910290024_Q00332_ROW. This is the latest update. There are no OTAs to apply. The M10 is due for a security OTA pretty soon, though. The P10 has already received it.
Unfortunately, it's no longer possible to post a direct link to Lenovo's website for this ROM. You'll have to use LMSA to get it.
FYI. Lenovo have changed how they serve the stock ROM. The ROM is now kept at rsdsecure-cloud.motorola.com. LMSA seems to generate (or request and receive) a one-off time-limited credentialed ticket for the download. You can't download the zip files without the credentials attached to the URL.
If you really want to, you can still intercept the URL in download_resources.json in the LMSA download folder.
is there anything new in the update. i might hold of because i dont want to lose root.
cbomb1337 said:
is there anything new in the update. i might hold of because i dont want to lose root.
Click to expand...
Click to collapse
No, there's nothing new. This isn't really an update, it just seems to be a consolidation of the old stock ROM and incremental OTAs.
This is only for M10 wifi (TB-X605F) with SDA450.
The latest OTA for TB-X605F has just landed. It's available on your tablet, or directly from: TB-X605F_USR_S210126_191029_Q00332_ROW_TO_TB-X605F_USR_S210152_200120_Q00332_ROW_WCE26E2CD5.zip.
The update takes the M10 to:
Code:
build: TB-X605F_USR_S210152_200120_ROW
security patch: 1 January 2020
kernel: 3.18.120-perf-gd60e12b6-dirty
If you have TWRP and root, you'll need to:
select "uninstall" in the Magisk Manager app
install the OTA (from SD card) in recovery and reboot
re-flash TWRP
re-install Magisk
only if you unencrypted the data partition
If you have unencrypted your data partition, it will be re-encrypted during this process. Make sure you back it up before you start the OTA. You might also need to restore the TWRP backup you made of the vendor partition, before the OTA will run. Once the OTA, TWRP and Magisk are installed, you can re-run the dm-verity tool.
This version of TWRP works on the Lenovo TB-X505F (wifi).
For the TB-X505X, see this thread. For the TB-X605F/L, see this thread.
For the TB-X606F/L, see this thread. The X606F/L is the second gen M10 and it uses a Mediatek SOC.
Code:
#include <std_disclaimer.h>
/*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Working:
AFAIK, everything is working including:
data decryption
MTP
Known issues:
time not adjusting for Daylight Saving
OTA (for a workaround see this post)
Before installing TWRP
Before you install TWRP, upgrade your tablet to the Android 9 (Pie) or Android 10 (Q) stock ROM.
This tablet shipped with Android 8 (Oreo), in which the bootloader did not allow unlocking. When you tried to unlock the bootloader, it gave this error message:
Code:
fastboot oem unlock-go
FAILED (remote: 'unknown command')
fastboot: error: Command failed
Installation
It is recommended that you also install Magisk. This will ensure TWRP remains your default recovery.
Step-by-step guide
download TWRP to your PC (see the Download section below)
download magisk.apk to your MicroSD or OTG device. Get the latest Magisk apk file here. Rename the filetype from apk to zip (for example Magisk-v22.0.zip)
if your bootloader is already unlocked, go to step 4. To unlock bootloader:
on tablet: go to Settings->System->About and press "Build number" 7 times to enable Developer Options.
on tablet: go to Settings->System->DeveloperOptions. Turn on: "OEM unlocking" and "USB debugging".
connect tablet to your computer. Tablet will ask for permission to "Allow USB debugging". Tick "always allow" and select "OK".
backup any files you want to keep to an external device (MicroSD/OTG/computer), because the next step will wipe all your photos, files, google account etc on the tablet.
Now unlock the bootloader:
Code:
adb reboot bootloader
fastboot oem unlock-go
fastboot reboot
flash the twrp image:
Code:
adb reboot bootloader
fastboot flash recovery twrp.img
if you haven't loaded Magisk yet, go to step 6. If you have already loaded Magisk, you can just reboot and you're finished:
Code:
fastboot reboot
adb reboot recovery
load Magisk (step one): reboot to recovery. Do not reboot into the system, because it will over-write TWRP with stock recovery. If that happens, go back to step 4 and start again. When you issue the reboot command (below), you have to immediately press the button combination to reboot to recovery (TWRP). Here are the steps:
issue the reboot command:
Code:
fastboot reboot
immediately press and hold all three buttons (Pwr+VolUp+VolDown). The tablet might reboot twice. Release all the buttons when you see the TWRP screen, or hear your PC acknowledge that ADB is connected.
load Magisk (step two): flash Magisk. In TWRP:
select "Install"
use "select storage" to locate device you stored magisk.zip on.
press the OK button
select the Magisk zip file
swipe to confirm Flash
when Magisk is finished, hit the "Reboot System" button
finished!
If you prefer to use button combos, rather than fastboot/ADB commands:
Vol Down + Power = fastboot mode
Vol Up + Vol Down + Power = recovery mode
Changelog
Code:
01/03/2023 - bug fix: data partition again backs up and restores correctly
20/01/2023 - add TW_EXTRA_LANGUAGES and TB_X505F_S001149_221115_ROW kernel (credit to @Tonyha7 )
30/12/2022 - add system partition to AdvancedWipe (TB_X505F_S001147_220830_ROW firmware only)
15/11/2022 - TWRP 3.7.0-0 update
- support for TB_X505F_S001147_220830_ROW
18/12/2021 - TWRP 3.6.0-0 update
- support for A12 decryption (keymaster)
27/03/2021 - TWRP 3.5.1-0 update
- change to landscape mode for tablets
01/01/2021 - TWRP 3.5.0-0: initial release
Downloads
TWRP 3.7.0-0 for X505F: twrp-X505F_11.img (for TB_X505F_S001147_220830_ROW and above)
TWRP 3.6.0-0 for X505F: twrp-X505F_11_2021.img (for earlier stock ROMs)
Source code
https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp/tree/twrp-11
https://github.com/Yahoo-Mike/recovery_device_lenovo_X505F/tree/android-11.0
Credits
The guys at TeamWin Recovery Project.
Everyone whose device trees I plagiarised from GitHub.
Contributors
Yahoo Mike
Tonyha7
Last Updated 2023-03-01 (fix /data backup/restore)
Created 2021-01-01
reserved
Thanks for useful post,
Possible to reboot into recovery from fastboot?
zubair1836 said:
Thanks for useful post,
Possible to reboot into recovery from fastboot?
Click to expand...
Click to collapse
Not that I know of. The bootloader accepts the command fastboot reboot recovery, but boots to system anyway.
Hello there, I've been looking how to install this on my slow tablet for almost like an hour. Could there be some tutorial or extended explanation to the process and installation, I'm such a noob, sorry.
This worked for me. Thank you for your effort and the TWRP!
Worked for me too - many thanks!
Can't wait for a custom ROM!
TWRP Recovery Installation Steps
1. Download android platform tools
2. Unlock developer mode on the M10
3. Enable USB debugging on the M10
3. OEM unlock enable on the M10
4. XDA download TWRP copy to sd
5. Download Magisk app (from Github!!! johnwu), change extension to .zip
6. Adb to fastboot
7. fastboot flash recovery [filename.img]
8. Turn off device
9. Turn on device holding all 3 buttons, release when see Lenovo splash screen
10. In TWRP find Magisk zip
11. Install Magisk
Stock ROM Recovery
1. Download qualcomm drivers 64 bit install
2. Download Lenovo recovery and image tool windows app from Lenovo support website
3. Fastboot oem edl
4. Turn off M10
5. Start recovery windows app, wait till instructions
6. Hold volume up (up is the side of the button closest to the front camera) and insert cable
7. Release button after windows app detects device
8. Troubleshoot by checking windows device manager for the M10 appears as a Qualcomm device
I'm thinking about getting one of these tablets, but before I do so I'd like to know that the screen lock still works after installing TWRP.
This might sound like a crazy question, but my Samsung Tab A won't set a screen lock - pattern, PIN or password - once TWRP has been installed, and I'd rather not run into the same issue again.
Heeni said:
I'm thinking about getting one of these tablets, but before I do so I'd like to know that the screen lock still works after installing TWRP.
This might sound like a crazy question, but my Samsung Tab A won't set a screen lock - pattern, PIN or password - once TWRP has been installed, and I'd rather not run into the same issue again.
Click to expand...
Click to collapse
Confirmed working normally.
zubair1836 said:
Confirmed working normally.
Click to expand...
Click to collapse
Many thanks.
Thank you! TWRP is working fine!
Stupid me flashed before I installed the Android 10 OTA, so I had to temporarily go back to stock recovery. Unfortunately beamingbadger's method didn't work for me.
This is how it worked for me:
Download the OTA via Lenovo's "Rescue And Smart Assistant"
The stock recovery image will be in the Download folder (default path: C:\ProgramData\LMSA\Download\RomFiles) called "recovery.img"
Flash the recovery.img the same way as you would with the twrp img (adb reboot bootloader -> fastboot flash recovery recovery.img)
fastboot reboot
Install OTA
Flash TWRP recovery + Magisk again (follow the steps from the first post, skip bootloader unlock)
The method I use to install OTAs is:
open Magisk App
select "Uninstall Magisk", then the "Restore Images" option
reboot to Android (you will have no root access and stock recovery is restored)
apply OTA
re-flash twrp and install Magisk
NOTE 1: if you've unencrypted your data partition, it will be re-encrypted by this process.
NOTE 2: the new Magisk App (v22) can be installed in TWRP by renaming the *.apk to *.zip. See the new install instructions.
What's involved with running gsi ROMs on this device? It's got the same SoC as my Samsung Tab, which runs them well, so I'm assuming that this tab will also, but I'd like to know if there are any traps that I need to be aware of.
I can partly answer my own question. It all went more smoothly than I expected: installing TWRP, Magisk and then LineageOS R Mod //LiR, followed by Disable_Dm-Verity_enfec.zip.
If I want to try other GSI ROMs, do I need to flash stock before trying another one? I've had some trouble doing that (won't boot) and it's possibly to do with encryption.
Heeni said:
I can partly answer my own question. It all went more smoothly than I expected: installing TWRP, Magisk and then LineageOS R Mod //LiR, followed by Disable_Dm-Verity_enfec.zip.
Click to expand...
Click to collapse
That's great news. Well done.
Heeni said:
If I want to try other GSI ROMs, do I need to flash stock before trying another one? I've had some trouble doing that (won't boot) and it's possibly to do with encryption.
Click to expand...
Click to collapse
On my X605F I do this in twrp for a new GSI install:
format (not wipe) data partition. This is the option where you have to confirm by swiping.
factory reset. This clears the caches.
restore the stock boot and vendor partitions (from a backup I made). This is because Magisk can touch these partitions.
install the GSI system image
install anything else I need like disable_Dm-Verity, Magisk, gapps etc
I don't know what LOS R Mod //LiR does to your system. If it touches any other partitions, you should restore those to stock too.
Thanks for that. It gives me something to go on with. I've downloaded the stock ROM from lolinet, so I can grab the boot and vendor images from that.
I was able to try a couple of other GSI ROMs and I've settled on AndyYan's LineageOS 17.1 for now. The only serious installation issue I had - which I can laugh about in hindsight - was thinking I'd got myself into a very bad bootloop, when all I needed to do was let go of the power button after the Lenovo logo appeared.
On this tablet, there is no navigation capability at all (no navbar, no gestures, no setting to configure them) on installation, and I have to set it using adb. I suspect it goes back to PHH basic ROMs, but I don't feel like doing yet another install and testing right at this moment. Is this happening on the other tablets that you're testing, or is it unique to this one?
I just posted the v3.5.1 update to twrp.
It's also changed to landscape mode, as many of you requested.
Quick question, how do i apply new system updates with twrp installed? Should i not bother? Also, i forgot how to block check for updates!
will this allow flashing of stock roms download from lenovo recovery? ive been stuck on an ancient android 9 version because the ota updater fails.
Since I had failed at all the instructions so far, I contacted ivan_meier.
With his very friendly help the s10e is now running on LOS 18.1; with Magisk and TWRP.
Status: Jan. 2022
Everything that follows is the knowledge of ivan_meier! (Honour to whom honour is due!). I only did the steps during the communication.
Before note: the Phone is reset, Format Data is made. Make thoughts about backup. I started from scratch!
Step 1: Odin flash FW (for me Samfw.com_SM-G970F_DBT_G970FXXSEFUL1_fac.zip)
Step 2: Boot the phone. Setup only minimal (no account (Google...) create, Phone about 10..15 min run let because during the data and init are updated in the background.
Step 3: Phone reboot and install Magisk.apk. Copy the AP-File from the firmware to the phone. Patience: this is about 5GB, it takes time.
Step 4: Turn on developer options, turn on USB debugging, on PC "adb devices", on Phone "always allow: yes".
Step 5: Phone in bootloader-mode, bootloader unlock (who does "yes" now sets Knox to "1" for ALL times. Please think carefully if you want this!
If you unlock the bootloader with "yes": the phone automatically does "factory reset & format data", so after startup setup again minimal.
Step 6: Start Magisk, install - patch file, select the AP in the phone and when Magisk is done it says WHERE the magisk_patched is located and HOW it is called.
Then copy it to PC. Patience: this is about 5GB that have to be patched and then copied to the PC.
Step 7: Put the phone in download mode, use Odin to flash the firmware "BL, CS, CSC and in AP the magisk_patched".
Step 8: Reboot the phone and install Magisk.apk. Magisk should now show "Yes" at Installed. But this is not important.
Step 9: Odin:
twrp from Samsung Galaxy S10e (Exynos) (insert into AP-slot in odin)
vbmeta index - powered by h5ai (insert into CP-slot in Odin)
deselect auto reboot,
when Odin is ready hold volume down and bixby and power, when phone goes off(screen goes black) switch from holding volume down to volume up
Phone starts in TWRP, keep holding it and keep it plugged into PC
first in TWRP format data (format it, wiping it is not enough)
then TWRP install this kernel
s10e – Google Drive
select kernel_11 OR kernel_12 (i have Android 11, i use kernel_11).
Reboot to System
"Unfortunately Magisk says "patch file". Which file? patched-AP is already flashed with Odin." (<--- my question to ivan)
extract boot.img from lineageos.zip, copy to Phone, let Magisk patch this file, boot to TWRP and flash this magisk-patched-boot.img to boot
reboot and look in magisk: now magisk says "installed (version)". (i use Magisk 23.0)
That was a bit longer way. But it works! At least for me.
Very important is "timing"! What good is a manual that was written a year ago? Samsung makes more and more "improvements".
The "modder scene" brings new helps with time.
Now I have a s10e with Magisk and TWRP and LOS 18.1 (tentatively previously installed a LOS 19.1 which is based on 18.1. I do not like it!)
Important: the TWRP is now up to date, vbmeta is in(against AVB!), and since I use lineage-18.1-20220120-nightly-beyond0lte-signed.zip the LOS-updater should be
the LOS-Updater should still bring the updates until the end of 18.1.
This all falls under "you can do - but you don't have to".
As always: everyone is responsible for what he does with his phone !!! YOUR Phone - your RISK !!!
Acknowledgement to: ivan_meier
Translated with www.DeepL.com/Translator (free version)
(plase excuse my englich - original write in german - translatet with deepl)
you have question: i will answer as best i can
Edit: Mod: thanks for moving
Edit: error 28.02.2022
"Holy Moly" it won't be long now and the s10e will be subjected to a mechanical treatment with the sledgehammer!
Installed was Magisk 23.0 / this morning looked at Magisk: 24.0 available. So back to the beginning and used Magisk 24.0.
Just runs again Magisk on 24.0 new - 24.1 available. (wild Words!!!). Again back to intercept with Magisk 24.1
Who puts a T in the next word after "Edit;" is not so wrong. I have already flirted with a s10. Forget it. I hope very much that other manufacturers offer a handy (under 6"). Then it's over with Samsung.
Translated with www.DeepL.com/Translator (free version)
Edit: error 30.01.2022
At the moment Magisk 24.1 is causing trouble. My eMail in K9 says "wrong certificate from t-online". This is not so with an Old-Phone with Magisk 23.0.
The s10e is switched off, replaced by an Old-Phone until Magisk runs stable again.
Edit: 05.02.2022 14:29 1 time did not pay attention during my experiments(Softwareupdater NOT deactivated) - now Android 12 is on it! At the moment the topic s10e is done for me. There are at least 30 hours of installation orgies in it. So much crap in one I never had so much crap in one device. I just got a Sony xperia 10 for testing. It now runs LOS 18.1, TWRP, Magisk 23.0. That was done within an hour.
Edit 09.03.2022 14:06 Next attempt (there is not much choice of max 6" in reasonable configuration).
Installed after https://wiki.lineageos.org/devices/beyond0lte/install; just replaced LOS recovery with TWRP.
LOS from LineageOS Downloads
Plus Magisk 24.1 (let's see how I get along with Zygisk).
LOS is running, waiting for the next update. Otherwise everything as usual.
If the s10e is no longer supported by LOS itself (1..2 years ?) I try a "Build your owen ROM" [ByoR].
2 ByoR already done on other devices. PC upgraded to 32GB. With 16GB it also works, but takes "a little bit slow".
(I am not a developer - only an ambitious user).
Translated with www.DeepL.com/Translator (free version)
Hi, I recommend to you to drop ivan_meler kanged rom and download LineageOS from download.lineageos.org/beyond0lte, the official lineage maintained by @Linux4
many people have many preferences. who prefers which custom-rom and why - is up to everyone.
the main thing is that he is satisfied with his custom-rom
i am prefer official lineageos-rom, another prefer another - thats is o.k.
it's nice when we have a choice
Hi
in which part do you flash lineage?
Just before we get started, I would like to say that you will not brick your device if you follow the steps as is without any, and I mean any deviations.
Read what works and what doesn't first!
Okay, enough preface, let's jump right in!
Firstly, pre-requisites(hardware):-
1.A micro SD card
2. A windows PC, windows 7 or later (32 or 64 bit)
3. A USB Type-C cable
4. A galaxy tab A7 running the latest one ui 4.x build
Pre-requisites (software on PC), you'll need:
1.Stock firmware:
Samsung Galaxy Tab A7 (LTE) Firmware Download SM-T505 Free Download
Samsung Galaxy Tab A7 (LTE) Firmware Download SM-T505 Free Download ⭐ Official and fast update ⭐ Max speed and free download ⭐ Best Samsung Galaxy website
samfw.com
Download the latest firmware from here
1.1 After downloading it, extract it on the PC and copy the AP file to your micro SD card, as we need it on the tab later
2. Samsung USB drivers
download them from here and install them on your pc, it'll take a while but it's essential for this process
https://developer.samsung.com/android-usb-driver
2.1 Reboot your PC after installing the drivers
3 Download the twrp.img from below
https://forum.xda-developers.com/t/...axy-tab-a7-10-4-sm-t500.4358595/post-87038713
(Yes, correct, download the .img as we won't be using Odin to flash custom recovery)
Copy this to your SD card as well
4. Download Canary apk of magisk delta from link below
https://huskydg.github.io/magisk-files/
Copy the apk to your microSD which has the previously extracted AP file
5. Download dynapatch from the file attached below credits to @redymedan for developing this!
Then move it to your micro SD card
6. Download the GSI image of your choice, and (make sure that it doesn't exceed 3.3GB after extraction) extract it from .img.xz format to .img format and then copy it to the micro SD card
(also, if it exceeds 3.3 GB, don't worry,follow the steps in important notes on how to expand your system partition to accommodate larger GSIs...)
7. If your gsi doesn't have gapps or you want to flash a system mod then download a vndklite variant of your gsi, as system is mounted as RW in vndklite gsi, where's system is mounted as read only in normal gsi images
8. Download Odin and extract it
https://samsungodin.com/
9. Download SmartPack kernel manager apk and copy it to the sdcard too
https://github.com/SmartPack/SmartPack-Kernel-Manager/releases
(We will be using this to flash twrp in a later step)
10. Download the brightness and watchdog fix module from below
Copy it to SD card
(Optional) 11. If you don't want your install storage encrypted, download the following two zips and move them to SD card,
[Pie/10/11] [System-as-root] Multidisabler: disables encryption, Vaultkeeper, auto-flash of stock recovery, proca, wsm, cass, etc.
The multi-disabler started life on the Exynos S10 range, the first Samsung devices to launch with Android 9 (Pie). Since then, it has grown to support a great many Samsung devices running either Android 9, 10 or 11, and with either an Exynos or a...
forum.xda-developers.com
https://zackptg5.com/downloads/archive/Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip
Process to flash GSI:
1) Unlock the bootloader
To unlock the bootloader, follow the steps from here...
https://forum.xda-developers.com/t/...4-unlock-bootloader-root-with-magisk.4185993/
2) After that patch the AP image we copied to the micro SD card earlier and then copy the patched ap to the micro sd card and then to the pc. Steps of patching can be found here
https://forum.xda-developers.com/t/...4-unlock-bootloader-root-with-magisk.4185993/
3) After patching the AP image, copy the patched image from downloads folder to your micro sd card
4. After that turn your device off
5. After the device is fully powered off, hold both volume up and volume down buttons simultaneously and connect it to your pc, then click volume up button once during the prompt to enter download mode
6) After entering download mode, select the BL, CP, and CSC (do not choose HOME_CSC!) files from the extracted firmware, after doing that, for AP, select the patched AP file we copied earlier and then click start on Odin.
7. After the flash is successfully finished, reboot your device and set it up, after setup install the magisk Canary apk from the micro SD card
8. After installing the apk, open it, and click 'OK' on additional setup prompt and the device will reboot after a few seconds
9. After the reboot completes, install the smart pack kernel manager apk we put in the SD card earlier, then open it, then, navigate to
Tools>Backup>(swipe to the right where it says "boot partition")> it changes to recovery partition> click on the plus symbol> two options show up, select the flash recovery option> select the twrp image from SD card (file manager opens automatically)> click on "select" and then flash it...
10. Then open magisk delta app, and reboot to recovery
11. After rebooting to recovery, flash dynapatch
12. Then reboot to recovery (very important)
(Optional)12.1 Flash multidisabler we downloaded earlier, along with disable dm Verity to disable FBE on integral storage. Also, if you intend to disable encryption, do flash both the zips not one.
13. Then select install>Micro SD Card>install image> select GSI image you downloaded> select System Image > swipe to flash, then factory reset and wipe data from within twrp (thank you @shorty9210 for the factory reset part!)
14. Here, hectic nature of you must be used...
15. Boot to your GSI, and set it up as fast as possible as a watchdog crash is triggered every 30-50 seconds which causes a reboot
16. Install magisk apk and reboot for additional setup
17. After reboot, open magisk and install the brightness and watchdog fix module
18. Reboot the device after installing module
19. At this point you won't get random reboots
20. Now you can enjoy your GSI...
Now, onto what works and what doesn't...
Working:
Boot
Touchscreen
Sound
WiFi
Bluetooth
Mobile data
Camera
Microphone
Doze
OTG
Power buttons
Volume buttons
Charging
Rotation
Gyroscope
Calling(works with VoIP)
Not working:
VoLTE
In call audio (in case of Sims)
Auto brightness
Offline charging
Untested:
Cast
USB tethering
MTP
Tested roms:
1. Trebledroid GSIs (don't use, as magisk doesn't work and gapps can't be properly installed for some reason)
2. Pixel experience ( magisk works and it's stable after running the watchdog command)
3. Google GSI (vanilla and Gapps, not recommended, due to it being extremely barebones and not having fixes for DT2W, and headsets)
4. Project Elixir (needs watchdog module, but mostly stable)
Now credits!
To team XDA for keeping this forum alive and well,
@phhusson for developing GSI images that actually made this possible
@topjohnwu for creating magisk
@agreenbhm for the TWRP image and for helping me,
@duyfken for correcting the firmware links, and also, for informing me to add the type of GSI for this device!
@shorty9210 for a correction
@huskydg for magisk delta development
And finally all other members of XDA for taking interest in the modding scene,
Thank you!
I'm quite new to the GSIs as a whole, so, I still can't find any workarounds for issues, I can only list them for everyone to know...
Important notes:
1. If your GSI has phh settings, do the following...
1.1 Enable double tap to wake
Settings>Phh Treble settings>Samsung features >Tick "Enable difficult tap to wake"
1.2 For making headphones work,
Settings>Phh Treble settings>Misc features>Tick "Use alternate way to detect headsets"
Also, Enable developer options>Enable "Disable Bluetooth A2DP hardware offload" and restart when prompted
2. If the gsi ROM you're trying to flash doesn't fit on current system partition, then,
*This process will wipe your system partition and will reset your recovery, so, keep the dynapatch zip and gsi image on hand, you will need it!*
Download latest platform tools from AOSP site, link below
https://developer.android.com/studio/releases/platform-tools
https://forum.xda-developers.com/t/...xy-tab-a7-10-4-sm-t500.4371123/#post-86050459
a) download the product.img from above link
b)Reboot to recovery from magisk app, then, in twrp, click on 'Reboot' button
c) click 'fastboot'
d) the device will now reboot and then after a few seconds, a twrp ui will appear with the text 'fastboot'
e) connect your device to a pc with the latest version of platform tools and drivers installed
f) run these commands in order
fastboot flash product product.img
fastboot erase system
fastboot resize-logical-partition system 3940000000
fastboot reboot recovery
g) after doing so, again reboot to recovery, flash dynapatch zip first
h) again reboot to recovery and flash your gsi image
i) this time images up to 3.9GB will be flashable
j) no need to format data if you're flashing same rom
And that's it you'll be able to enjoy bigger ROMs on your Galaxy Tab A7!
3. follow steps from here to get 4-speaker audio!
Post in thread '[ROM][SM-T500] Samsung Galaxy Tab A7 10.4 (2020) - LineageOS 19.1 (and TWRP 3.6.1)'
[ROM][SM-T500] Samsung Galaxy Tab A7 10.4 (2020) - LineageOS 19.1 (and TWRP 3.6.1)
Hello world, I have successfully built LineageOS 19.1 with Gapps for the SM-T500 (Tab A7 10.4 2020) using Andy Yan's LOS GSIs. Lineage is current as of 3/24/2022. I have also compiled TWRP version 3.6.1, based on Android 11 (previous release...
forum.xda-developers.com
4. Previously, we had to use either some magisk modules or SmartPack kernel manager to enable swap so that the device won't crash under load, but, now, 2GB of swap is allocated by default, which is plenty sufficient for daily usage, so, i recommend you not to use any modules or services that enable swap....
5. If zygisk is enabled after module is installed, some users reported that it breaks brightness fix, to remedy that, try flashing permissiver_v5 from below in twrp
Permissiver_v5.zip | by erfanoabdi for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
6. Also, please do not rely on extra dim if brightness fix module won't work, try above step , i did this previously and the edges of my screen got ruined(ghost imaging) due to the heat...
7. Please refrain from using any modules that spoof the device identity as it causes the phh Treble app to not display "Samsung features" at which point you can't use DT2W, so beware...
8. Recommended settings in magisk delta
a)magisk delta>settings>hide magisk app, you will be prompted to allow magisk delta to install apps, allow it and start the hiding> now, the magisk app will be under an alias you chose
b)magisk delta>settings>Zygisk(enable)
c)magisk delta>settings>Bootloop Protection (enable)
d)magisk delta>settings>Magisk Hide
9. Passing safetynet on Gapps GSIs
a)magisk delta>settings>Configure MagiskHide> now, tap on three dots, elect show system apps>then tick the boxes next to the following apps
Google Play Store, Google Play Services, Google Services Framework
b) Install the magisk module "shamiko" version 0.5.2, as later version causes Google services to crash... Download link below(warning, shamiko 0.6 causes all Google services to crash, also, is no longer working with magisk delta, so, use magiskhide present in the delta version)
https://github.com/LSPosed/LSPosed.github.io/releases/tag/shamiko-120
(Optional) You can also install this module below after installing shamiko for a higher chance to not fair safetynet randomly...
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
c) After installing the module, reboot
d) clear data and cache for Google Play Store, Google Play Services, Google Services Framework
e) at this point you should pass safetynet successfully
10. Just a heads up, be sure to only download GSIs from the list in @phhusson GitHub, i.e, link below,
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
And, do not spend money on people that claim to give the "best GSIs" or whatever gibberish they use, only spend money as a donation to a developer, if you really enjoy their work, and would like to support them to keep up thier interest!
I had to mention this to put you on the cautious side of things!
11. Taskbar height is incorrect on some roms, and the magisk module from below link fixes it, credits to @wEER1234 for mentioning this, and to @Coxxs for delaying developing it!
Releases · Coxxs/hide-tablet-taskbar
A Magisk module to hide tablet gesture bar and more [Android 12.1+] - Coxxs/hide-tablet-taskbar
github.com
12. This is for improving the longevity of your device
12.1 To prolong the lifespan of your battery, install the "acc" magisk module, reboof, open a root terminal and run the following commands
acc -s mcc=200
acc -s mcc=3900
The first command limits the charging current to 200 mA and charges the battery at a power of 1.8W which greatly reduces the strain and heat evolved by the battery, and the second command only allows your battery to charge up to 3.9v (52%), as according to battery University, maximum cycles can be achieved by maintaining the voltage battery 3.9 and 3.7
12.2 This is to reduce the Power and heat evolved by the processor
Install smart pack kernel manager, grant root access, go to cpu section, and do the following
Big cpu cores:
Maximum frequency:1056Hz
Minimum frequency:902Hz
Little cpu cores:
Maximum frequency: 1017Hz
Minimum frequency:864Hz
At these frequencies the device stays stable and relatively less hot than at higher clocks...
* This guide is present for legacy reasons, use the guide in the first post *
Just before we get started, I would like to say that you will not brick your device if you follow the steps as is without any, and I mean any deviations.
Read what works and what doesn't first!
Okay, enough preface, let's jump right in!
Firstly, pre-requisites(hardware):-
1.A micro SD card
2. A windows PC, windows 7 or later (32 or 64 bit)
3. A USB Type-C cable
4. A Samsung galaxy tab a7 running Android 11 with January 2022 Security Patch
Pre-requisites (software on the pc), you'll need:-
1.Stock firmware:
Samsung Galaxy Tab A7 (LTE) Firmware Download SM-T505 Free Download
Samsung Galaxy Tab A7 (LTE) Firmware Download SM-T505 Free Download ⭐ Official and fast update ⭐ Max speed and free download ⭐ Best Samsung Galaxy website
samfw.com
from this link, select your respective country and download the firmware with January 2022 security patch level, then download it
1.1 After downloading it, extract it on the PC and copy the AP file to your micro SD card, as we need it on the tab later
2. Samsung USB drivers
download them from here and install them on your pc, it'll take a while but it's essential for this process
Samsung Android USB Driver | Samsung Developers
You need the driver only if you are developing on Windows and want to connect a Samsung Android device to your development environment over USB.
developer.samsung.com
2.1 Reboot your PC after installing the drivers
3. Download TWRP 3.6.1 beta 5 from here
[ROM][SM-T500] Samsung Galaxy Tab A7 10.4 (2020) - LineageOS 19.1 (and TWRP 3.6.1)
Hello world, I have successfully built LineageOS 19.1 with Gapps for the SM-T500 (Tab A7 10.4 2020) using Andy Yan's LOS GSIs. Lineage is current as of 3/24/2022. I have also compiled TWRP version 3.6.1, based on Android 11 (previous release...
forum.xda-developers.com
this is our custom recovery
4. Download magisk Canary apk from here
GitHub - topjohnwu/Magisk: The Magic Mask for Android
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
And copy the apk to your micro SD card
5. Download the SM-T500-GSI-kernel.zip from here
[Guide][SM-T500] Galaxy Tab A7 10.4 - Flash LineageOS or any other GSI rom.
These are instructions to flash LineageOS 18.1 GSI builds on our SM-T500. The same instructions should work for any other GSI rom out there. Some instructions here, like flashing an empty product.img and resizing system partition, are not...
forum.xda-developers.com
And copy this file to your micro SD card
6. Download dynapatch from the file attached below credits to @redymedan for developing this!
Then move it to your micro SD card
7. Download the GSI image of your choice, and (make sure that it doesn't exceed 3.3GB after extraction) extract it from .img.xz format to .img format and then copy it to the micro SD card
7.1 If your gsi doesn't have gapps or you want to flash a system mod (eg. Brightness fix) then download a vndklite variant of your gsi, as system is mounted as RW in vndklite gsi, where's system is mounted as read only in normal gsi images
GSI type should be "arm64_ab" if you want to you can also use vndklite variant!
8. Download Odin and extract it
Samsung Odin - Official Odin Download links
Samsung Odin, Official Odin Download links and flashing guides
samsungodin.com
These are all the pre requisites, and yes, every single one is required.
Process to flash GSI:
1) Unlock the bootloader
To unlock the bootloader, follow the steps from here...
[Guide][SM-T500/T505] Galaxy Tab A7 10.4 - Unlock Bootloader & Root with Magisk
I recently purchased the Galaxy Tab A7 10.4 (released in 2020) and couldn't help but notice that there's no dedicated thread in the forums for unlocking the bootloader or rooting (Although, the method should be very similar to what is followed...
forum.xda-developers.com
2) After that patch the AP image we copied to the micro SD card earlier and then copy the patched ap to the micro sd card and then to the pc. Steps of patching can be found here
[Guide][SM-T500/T505] Galaxy Tab A7 10.4 - Unlock Bootloader & Root with Magisk
I recently purchased the Galaxy Tab A7 10.4 (released in 2020) and couldn't help but notice that there's no dedicated thread in the forums for unlocking the bootloader or rooting (Although, the method should be very similar to what is followed...
forum.xda-developers.com
3. After patching the AP image, copy the patched image from downloads folder to your micro sd card
4. After that turn your device off
5. After the device is fully powered off, hold both volume up and volume down buttons simultaneously and connect it to your pc, then click volume up button once during the prompt to enter download mode
6) After entering download mode, select the BL, CP, and CSC (do not choose HOME_CSC!) files from the extracted firmware, after doing that, for AP, select the patched AP file we copied earlier and then click start on Odin.
7. After the flash is successfully finished, reboot your device and set it up, after setup install the magisk Canary apk from the micro SD card
8. After installing the apk, open it, and click 'OK' on additional setup prompt and the device will reboot after a few seconds
9. After the device starts up, turn it off again, and put it in download mode by holding both volume buttons simultaneously and then connecting it to your pc
10. After that, uncheck everything in Odin except AP, and select the TWRP file we downloaded as the AP file, and then click start
11. After the flash is complete, turn the device off and then hold power+volume up and then immediately connect it to your pc immediately
12. You will get warning about custom binary, and xyz, but ignore it and press power button once, then you'll enter the TWRP recovery
13. After entering TWRP flash the dynapatch zip file from your micro SD card
14. After flashing it. use the reboot to recovery option
15. After you device booted to recovery again, go to Wipe>Advanced Wipe and then wipe dalvik cache and cache partition
16. After wiping them, go back to the install section, click on install image
17. After that select your GSI .img file you extracted earlier
18. Then it will ask you on which partition it should flash the image onto
19. You have to select 'System Image' partition (if it isn't available, then flash dynapatch again and reboot to recovery, do it as may times until the System Image partition shows up)
20. Then swipe to flash it,
21. After it flashes, go back to install and install the T500 Kernel zip we put in the micro SD card earlier (this is to prevent reboots after a few seconds)
22. And bam, you're done, set the GSI up, and enjoy!
Now, let's get onto what works and what doesn't
What works:- (will add more as I keep testing)
Boot
Touchscreen
SD Card
Cameras
Speaker (follow point 7 in additional notes for 4-speaker audio!)
Headphones (disable A2DP offload in PHH settings first)
Wifi
Bluetooth
Mobile data
Wifi hotspot
Microphone
Power button
Volume Buttons
4G mobile data (go to mobile networks and select preferred network as 4G first)
Auto rotation
Extra dim
SMS
Charging
HW acceleration
MTP
USB Tethering
OTG
Brightness*
( Run these commands in a terminal emulator
su
echo 100 > /sys/class/backlight/panel0-backlight/brightness)(this is not persistent you have to run this everytime you reboot or you can setup a script or something that runs it during boot time itself)
What doesn't work:-
VoLTE
In call audio
Tested roms:
1. Pixel experience
2.ProtonAOSP
3.crDroid
4. Lineage OS
Not tested:-
Cast (i can't test this I don't have anything to cast to)
* Also be sure to read the important notes as it has highlighted some common issues and their workarounds...
Now credits!
To team XDA for keeping this forum alive and well,
@phhusson for developing GSI images that actually made this possible
@topjohnwu for creating magisk
@agreenbhm for the TWRP image and for helping me,
@duyfken for correcting the firmware links, and also, for informing me to add the type of GSI for this device!
And finally all other members of XDA for taking interest in the modding scene,
Thank you!
I'm quite new to the GSIs as a whole, so, I still can't find any workarounds for issues, I can only list them for everyone to know...
Important notes:-
1) if you are stuck in twrp after selecting reboot to system, then go to Advanced>Terminal and type exit_twrp and then reboot to system
2)The brightness patch has not worked for me on any gsi vndklite or normal, so, if it works for you then you are lucky, if not then I have informed you (brightness fix is in the initial post!)
3) I didn't try OTA updates as we used dynapatch and I'm skeptical about OTAs, so, i recommend you to dirty flash any new releases normally from twrp
4) Disable 'A2DP hardware offload' in Phh Settings>Misc settings and check the box next to disable A2DP offload and then do the same in developer settings too
5) Themed icons causes lags and causes some apps to lock the device up, so, proceed with caution
6) If the gsi ROM you're trying to flash doesn't fit on current system partition, then,
*This process will wipe your system partition and will reset your recovery, so, keep the dynapatch zip and gsi image on hand, you will need it!*
a) Download twrp from the link below (as it has fastboot)
[RECOVERY][UNOFFICIAL]TWRP 3.6.0 for 2020 Galaxy Tab A7 10.4[SM-T500]
/* * Disclaimer * * Your warranty is now void. * * We're not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features...
forum.xda-developers.com
b) Also download the product.img file from the above link
c) Flash this recovery from existing twrp
d) boot to this new twrp
e) here, click on 'Reboot' button
f) click 'fastboot'
g) the device will now reboot and then after a few seconds, a twrp ui will appear with the text 'fastboot'
h) connect your device to a pc with the latest version of platform tools and drivers installed
i) run these commands in order
fastboot flash product product.img
fastboot erase system
fastboot resize-logical-partition system 3940000000
fastboot reboot recovery
j) after doing so, again reboot to recovery, flash dynapatch zip first
k) again reboot to recovery and flash your gsi image
l) this time images up to 3.9GB will be flashable
m) no need to format data if you're flashing same rom
And that's it you'll be able to enjoy bigger ROMs on your Galaxy Tab A7!
Credit goes to @paziusss for this!
7) follow steps from here to get 4-speaker audio!
Post in thread '[ROM][SM-T500] Samsung Galaxy Tab A7 10.4 (2020) - LineageOS 19.1 (and TWRP 3.6.1)' https://forum.xda-developers.com/t/...eos-19-1-and-twrp-3-6-1.4421365/post-86917225
8. To flash gapps you need to have a Vndklite variant of GSI installed, then, grab your favourite set of gapps (Android 12L/12) depending on your rom and flash them from twrp!
9. For more fluid performance, download "Smart Pack Kernel Manager" from fdroid, open it grant root access, then go to the hamburger menu, select Vritual memory, and move the slider to 2048 mb, then, enable apply on boot, and reboot your device!
Well, I'm back everyone, and I'll be updating the post #1 with new instructions with regards to running Android 13 GSIs, and post #2 contains the old guide in case someone needs it!
Wow. Thank u very very much..will prepared guide ...every thing is clear
One thing i might clarify which is found on pazinuss. Guide. Where he put kernell
Q: Which GSI variant should I choose?
A: arm64 ab. Use the vndklite variant if you want to flash gapps or fix the brightness
The brightness fix is there with kernel also .
Thank you .....🖐️🖐️
drsanusi said:
Wow. Thank u very very much..will prepared guide ...every thing is clear
One thing i might clarify which is found on pazinuss. Guide. Where he put kernell
Q: Which GSI variant should I choose?
A: arm64 ab. Use the vndklite variant if you want to flash gapps or fix the brightness
The brightness fix is there with kernel also .
Thank you .....🖐️🖐️
Click to expand...
Click to collapse
I didn't mention it, as I found out that extra dim intensity control does the job just fine, but I'll add it in either way, thanks!
Hausemaster said:
I didn't mention it, as I found out that extra dim intensity control does the job just fine, but I'll add it in either way, thanks
Click to expand...
Click to collapse
What i mean for who want to flash gapps or root by magisk or flash any file to the rom (vndklite) only support flashing because it is mounted Read and Write but others are Read only .
Thank you
drsanusi said:
What i mean for who want to flash gapps or root by magisk or flash any file to the rom (vndklite) only support flashing because it is mounted Read and Write but others are Read only .
Thank you
Click to expand...
Click to collapse
We initially patched AP file initially, so, magisk will be available even after you flash a gsi but yeah you're correct about the gapps part, I forgot about them as I'm using a Pixel experience gsi, I'll add in the part about vndklite, thanks!
Edit: added it!
Again after step 7 when restart ...the message. (only official binary vbmeta allowed). In red .????.
So disturbing .i do googled revise my steps .even on odin this appear.
On thing i noticed. In developer mode .the oem unlock tab not appear at all.. but before was there ....what i miss ?? Any suggestions
drsanusi said:
Again after step 7 when restart ...the message. (only official binary vbmeta allowed). In red .????.
So disturbing .i do googled revise my steps .even on odin this appear.
On thing i noticed. In developer mode .the oem unlock tab not appear at all.. but before was there ....what i miss ?? Any suggestions
Click to expand...
Click to collapse
Did you boot to system and verify that bootloader was in fact unlocked, as, vaultkeeper will lock bootloader if you don't boot to system after unlocking...
Edit: if you directly flashed without booting, bootloader will relock and you have to wait for 7 days for OEM unlocking to be available again...
Now. After few days of lineage 19
Works like charm wow ...i am happy how lineage rom evolved over these years .
My main concern is battery life i left the tab for 24hr no any drop at all.before on stock was strange drop .
Other things . brightness fix didnt work .
Now one quistion ..if i want to try another one rom what i do .? From the bigening or what step i start
Thank u in advance
drsanusi said:
Now. After few days of lineage 19
Works like charm wow ...i am happy how lineage rom evolved over these years .
My main concern is battery life i left the tab for 24hr no any drop at all.before on stock was strange drop .
Other things . brightness fix didnt work .
Now one quistion ..if i want to try another one rom what i do .? From the bigening or what step i start
Thank u in advance
Click to expand...
Click to collapse
If you want to try another ROM, I suggest you to start from setup 15
drsanusi said:
Now. After few days of lineage 19
Works like charm wow ...i am happy how lineage rom evolved over these years .
My main concern is battery life i left the tab for 24hr no any drop at all.before on stock was strange drop .
Other things . brightness fix didnt work .
Now one quistion ..if i want to try another one rom what i do .? From the bigening or what step i start
Thank u in advance
Click to expand...
Click to collapse
Also, the battery drop may be because of GSI roms not setting cpu frequency according to usage, it just locks it at full frequency causing heat and heavy battery drain, try lowering clockspeeds using a kernel manager
edit: I use smart pack kernel manager
drsanusi said:
Now. After few days of lineage 19
Works like charm wow ...i am happy how lineage rom evolved over these years .
My main concern is battery life i left the tab for 24hr no any drop at all.before on stock was strange drop .
Other things . brightness fix didnt work .
Now one quistion ..if i want to try another one rom what i do .? From the bigening or what step i start
Thank u in advance
Click to expand...
Click to collapse
I found the actual brightness fix from the thread which we downloaded kernel from, I added the commands in the OP here...
If you're flashing big GSIs and flash fails due to insufficient system space, I've added a way to do so in the important notes...
Hausemaster said:
Just before we get started, I would like to say that you will not brick your device if you follow the steps as is without any, and I mean any deviations.
Read what works and what doesn't first!
Okay, enough preface, let's jump right in!
Firstly, pre-requisites(hardware):-
1.A micro SD card
2. A windows PC, windows 7 or later (32 or 64 bit)
3. A USB Type-C cable
4. A Samsung galaxy tab a7 running Android 11 with January 2022 Security Patch
Pre-requisites (software on the pc), you'll need:-
1.Stock firmware:
Samsung Galaxy Tab A7 (Wi-Fi) Firmware Download SM-T500 Free Download
Samsung Galaxy Tab A7 (Wi-Fi) Firmware Download SM-T500 Free Download ⭐ Official and fast update ⭐ Max speed and free download ⭐ Best Samsung Galaxy website
samfw.com
from this link, select your respective country and download the firmware with January 2022 security patch level, then download it
1.1 After downloading it, extract it on the PC and copy the AP file to your micro SD card, as we need it on the tab later
2. Samsung USB drivers
download them from here and install them on your pc, it'll take a while but it's essential for this process
https://developer.samsung.com/android-usb-driver
2.1 Reboot your PC after installing the drivers
3. Download TWRP 3.6.1 beta 5 from here
[ROM][SM-T500] Samsung Galaxy Tab A7 10.4 (2020) - LineageOS 19.1 (and TWRP 3.6.1)
Hello world, I have successfully built LineageOS 19.1 with Gapps for the SM-T500 (Tab A7 10.4 2020) using Andy Yan's LOS GSIs. Lineage is current as of 3/24/2022. I have also compiled TWRP version 3.6.1, based on Android 11 (previous release...
forum.xda-developers.com
this is our custom recovery
4. Download magisk Canary apk from here
https://github.com/topjohnwu/Magisk
And copy the apk to your micro SD card
5. Download the SM-T500-GSI-kernel.zip from here
[Guide][SM-T500] Galaxy Tab A7 10.4 - Flash LineageOS or any other GSI rom.
These are instructions to flash LineageOS 18.1 GSI builds on our SM-T500. The same instructions should work for any other GSI rom out there. Some instructions here, like flashing an empty product.img and resizing system partition, are not...
forum.xda-developers.com
And copy this file to your micro SD card
6. Download dynapatch from the file attached below credits to @redymedan for developing this!
Then move it to your micro SD card
7. Download the GSI image of your choice, and (make sure that it doesn't exceed 3.3GB after extraction) extract it from .img.xz format to .img format and then copy it to the micro SD card
7.1 If your gsi doesn't have gapps or you want to flash a system mod (eg. Brightness fix) then download a vndklite variant of your gsi, as system is mounted as RW in vndklite gsi, where's system is mounted as read only in normal gsi images
8. Download Odin and extract it
Samsung Odin - Official Odin Download links
Samsung Odin, Official Odin Download links and flashing guides
samsungodin.com
These are all the pre requisites, and yes, every single one is required.
Process to flash GSI:
1) Unlock the bootloader
To unlock the bootloader, follow the steps from here...
https://forum.xda-developers.com/t/...4-unlock-bootloader-root-with-magisk.4185993/
2) After that patch the AP image we copied to the micro SD card earlier and then copy the patched ap to the micro sd card and then to the pc. Steps of patching can be found here
[Guide][SM-T500/T505] Galaxy Tab A7 10.4 - Unlock Bootloader & Root with Magisk
I recently purchased the Galaxy Tab A7 10.4 (released in 2020) and couldn't help but notice that there's no dedicated thread in the forums for unlocking the bootloader or rooting (Although, the method should be very similar to what is followed...
forum.xda-developers.com
3. After patching the AP image, copy the patched image from downloads folder to your micro sd card
4. After that turn your device off
5. After the device is fully powered off, hold both volume up and volume down buttons simultaneously and connect it to your pc, then click volume up button once during the prompt to enter download mode
6) After entering download mode, select the BL, CP, and CSC (do not choose HOME_CSC!) files from the extracted firmware, after doing that, for AP, select the patched AP file we copied earlier and then click start on Odin.
7. After the flash is successfully finished, reboot your device and set it up, after setup install the magisk Canary apk from the micro SD card
8. After installing the apk, open it, and click 'OK' on additional setup prompt and the device will reboot after a few seconds
9. After the device starts up, turn it off again, and put it in download mode by holding both volume buttons simultaneously and then connecting it to your pc
10. After that, uncheck everything in Odin except AP, and select the TWRP file we downloaded as the AP file, and then click start
11. After the flash is complete, turn the device off and then hold power+volume up and then immediately connect it to your pc immediately
12. You will get warning about custom binary, and xyz, but ignore it and press power button once, then you'll enter the TWRP recovery
13. After entering TWRP flash the dynapatch zip file from your micro SD card
14. After flashing it. use the reboot to recovery option
15. After you device booted to recovery again, go to Wipe>Advanced Wipe and then wipe dalvik cache and cache partition
16. After wiping them, go back to the install section, click on install image
17. After that select your GSI .img file you extracted earlier
18. Then it will ask you on which partition it should flash the image onto
19. You have to select 'System Image' partition (if it isn't available, then flash dynapatch again and reboot to recovery, do it as may times until the System Image partition shows up)
20. Then swipe to flash it,
21. After it flashes, go back to install and install the T500 Kernel zip we put in the micro SD card earlier (this is to prevent reboots after a few seconds)
22. And bam, you're done, set the GSI up, and enjoy!
Now, let's get onto what works and what doesn't
What works:- (will add more as I keep testing)
Boot
Touchscreen
SD Card
Cameras
Speaker
Headphones (disable A2DP offload in PHH settings first)
Wifi
Bluetooth
Mobile data
Wifi hotspot
Microphone
Power button
Volume Buttons
4G mobile data (go to mobile networks and select preferred network as 4G first)
Auto rotation
Extra dim
SMS
Charging
HW acceleration
MTP
USB Tethering
OTG
Brightness*
( Run these commands in a terminal emulator
su
echo 100 > /sys/class/backlight/panel0-backlight/brightness)(this is not persistent you have to run this everytime you reboot or you can setup a script or something that runs it during boot time itself)
What doesn't work:-
VoLTE
In call audio
Haptic Feedback (vibration)
Not tested:-
Cast (i can't test this I don't have anything to cast to)
* Also be sure to read the important notes as it has highlighted some common issues and their workarounds...
Now credits!
To team XDA for keeping this forum alive and well,
@phhusson for developing GSI images that actually made this possible
@topjohnwu for creating magisk
@agreenbhm for the TWRP image and for helping me,
And finally all other members of XDA for taking interest in the modding scene,
Thank you!
Click to expand...
Click to collapse
Also! This tab does not have a Vibration motor so you might wanna remove that from the "What doesn't work:-" List.
wEER1234 said:
Also! This tab does not have a Vibration motor so you might wanna remove that from the "What doesn't work:-" List.
Click to expand...
Click to collapse
I didn't know that this didn't have one, thanks for the information, will do the necessary changes now!
This may be a silly question, but why exactly are we using the SM-T500 firmware here and not the SM-T505 firmware?
Samsung Galaxy Tab A7 (LTE) Firmware Download SM-T505 Free Download
Samsung Galaxy Tab A7 (LTE) Firmware Download SM-T505 Free Download ⭐ Official and fast update ⭐ Max speed and free download ⭐ Best Samsung Galaxy website
samfw.com
duyfken said:
This may be a silly question, but why exactly are we using the SM-T500 firmware here and not the SM-T505 firmware?
Samsung Galaxy Tab A7 (LTE) Firmware Download SM-T505 Free Download
Samsung Galaxy Tab A7 (LTE) Firmware Download SM-T505 Free Download ⭐ Official and fast update ⭐ Max speed and free download ⭐ Best Samsung Galaxy website
samfw.com
Click to expand...
Click to collapse
The firmware is of the t505 version, only the kernel, recovery and other stuff is from t500 as they work and are the only resources available for this device...
Edit: The link preview itself mentioned SM-T505, so, yeah...
Hausemaster said:
The firmware is of the t505 version, only the kernel, recovery and other stuff is from t500 as they work and are the only resources available for this device...
Edit: The link preview itself mentioned SM-T505, so, yeah...
Click to expand...
Click to collapse
I ask as Post 1 instructions has SM-T500 firmware, hence why I linked the SM-T505 firmware here.
Also for reference for those trying to work out which type of GSI image to get when downloading one (from a stock as a rock SM-T505):
{
"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"
}
duyfken said:
I ask as Post 1 instructions has SM-T500 firmware, hence why I linked the SM-T505 firmware here.
Also for reference for those trying to work out which type of GSI image to get when downloading one (from a stock as a rock SM-T505):
Click to expand...
Click to collapse
Oh my! Thanks for the sharp observation, I corrected it now in the OP
Edit: I also added the type of GSI that should be used for this device!
Edit 2: I also mentioned you in the credits, as you're the one who caught the errors! And once again, thank you very much for the corrections you saved the day!