Related
Hey Guys,
I have been getting an 18MB OTA for my Micromax AndroidOne. However the update keeps failing. I have captured the OTA. The lInk is:
Update to LMY47K
The update failed maybe because I was rooted. But then I factory reset the phone so now, Root should technically be gone. Before doing factory reset, I had also removed root from the SU app. Still, when I try to install OTA update, I am getting an error. So I Captured the OTA and then tried to flashed the zip via recovery as well as ADB Sideload. Both of them gave the same error at the Verifying Current System stage:
Verifying current system...
"/system/bin/install-recovery.sh" has unexpected contents.
E:Error in /sideload/package.zip
(Status 7)
Installation Aborted
The same error occurs every time via both flashing methods. Any idea guys??
Thanks
PLEASE FLASH ON YOUR WON RISK. I AM NOT RESPONSIBLE FOR ANY DAMAGE THAT MAY BE CAUSED TO YOUR PHONE
Finally
DO THE FOLLOWING AT YOUR OWN RISK. I AM NOT RESPONSIBLE IF YOU BRICK OR DAMAGE YOUR PHONE
Finally it's done. I did the following steps: (Obviously backup data first)
1. I Unlocked the bootloader *LOST ALL DATA AS EXPECTED*
2. Flashed Philz Recovery (You can install any other but this recovery will be lost once flashing official zip as a result making Official Stock ROM and Official Stock Recovery)
Did these above 2 steps using AndroidOne Tool Kit. There are thorough instructions and warning to do so.
3. Downloaded the official update file from here. Only LMY47O file. Copied it on an External SD card
4. Go to Philz recovery, Select Wipe and then Clean to Install ROM (Preferably without inserting the SD Card).
5. Now insert the SD card, wait for a minute for the recovery to recognize your card and then select, Install Zip and then select from SD Card. Select your zip files, confirm installation.. Reboot once done
6. Once done, you will have a brand new OS. Enter all the information. and you will get the next two updates OTA and get installed just fine
Enjoy Your latest update!!
ashhem said:
DO THE FOLLOWING AT YOUR OWN RISK. I AM NOT RESPONSIBLE IF YOU BRICK OR DAMAGE YOUR PHONE
Finally it's done. I did the following steps: (Obviously backup data first)
1. I Unlocked the bootloader *LOST ALL DATA AS EXPECTED*
2. Flashed Philz Recovery (You can install any other but this recovery will be lost once flashing official zip as a result making Official Stock ROM and Official Stock Recovery)
Did these above 2 steps using AndroidOne Tool Kit. There are thorough instructions and warning to do so.
3. Downloaded the official update file from here. Only LMY47O file. Copied it on an External SD card
4. Go to Philz recovery, Select Wipe and then Clean to Install ROM (Preferably without inserting the SD Card).
5. Now insert the SD card, wait for a minute for the recovery to recognize your card and then select, Install Zip and then select from SD Card. Select your zip files, confirm installation.. Reboot once done
6. Once done, you will have a brand new OS. Enter all the information. and you will get the next two updates OTA and get installed just fine
Enjoy Your latest update!!
Click to expand...
Click to collapse
Justcopying and pasting from www.dileepworld.blogspot.com isillegal...you better know that!
nexi4droid said:
Justcopying and pasting from www.dileepworld.blogspot.com isillegal...you better know that!
Click to expand...
Click to collapse
Hi nexi4droid, greetings of the day.
A few points:
1. I have NOT copied this stuff from anywhere. I have written it myself. However it is but OBVIOUS that the instructions are very similar to other present ALL OVER THE WEB as that is how it is done.
2. Also, as you must have seen, I have given links to official pages of toolkits or OTA captures from where I have taken stuff. If I wanted to "just Copy-Paste", I would not have done so. I am well aware of how much efforts you developers take to bring us custom ROMS and special tools. So, No I am not the type of guy that steals or copies other people's work
3. I went through the link you have given and I could not find identical instructions anywhere on that beautifully blog. But then again, as I said in the first point. That is how it is done so you will find similar instructions all over the web.
4. And finally, My post is OLDER!! than your http://dileepworld.blogspot.in/2015/08/solution-for-canvas-a1-getting-back-ota.html So if anything, I should be blaming you, not me. But I wont as it does not make any sense. Everyone reads things from different places and tries various things the find on the web and then finally may post what worked for them. I did the same in my words taking part instructions from 1cefire's post and the AndroidOne Toolkit (Links in the OP).
I hope I have cleared my self and have no intention to offend you. Have a great day
Hi!
!! This is quite serious! I need to get my data (pictures, videos) out of my phone, which is possibly soft-bricked.
I did the following in hope of more usage opportunities with my new phone:
[Unlocked bootloader + Rooted it]
1. installed TWRP following this guide https://forum.xda-developers.com/p10/development/testers-twrp-t3585256;
2. rooted following this guide https://forum.xda-developers.com/p10/help/root-huawei-p10-p10-t3589946;
3. installed few apps like greenify, wi-fi hacking apps etc, and everything was good.
BUT then 1 app (don't remember which) requested that it needs SuperSU and not the one root permission app that I had. So it asked whether I want to install it. I thought - yes, why not. Then it said that before it can install SuperSU it needs to uninstall previous permission app - I clicked OK. Then it kind of started, but then failed the installation. Ok, I kind of closed it and there were no problems. But after next restart of the phone it was stuck on boot process..
I dont really care about the phone, but data on it is so important. I tried sme fast hend methrods to boot it, like wiping catch, dalvik catch, but it did not work out.
Next I looked for possobilities to rescue data, but I didn't succeed.
Easiest mentioned option - to enter twrp and connect via usb seemed promising, BUT data are shown encrypted.
Please see the picture - I tried to be as precise as I could, so that you can understand the situation.
! I can beckup all data to micro sd card, but would it decrypt after new install of stock rom (e.g. from eRecovery that Huawei provides) and allow access or not?
Please help me. I am willing to have 1-on-1 skype chat and give some donations for this as it is so important.
To mention: Rescue apps like EaseUS seems to be useless, because they state to recover data from bricked device, but then after installing soft it askes to allow usb-debbuging, but c'mon, it's not booting up.. .
So,
1. Is there a chance to recover data?
2. Is it a good sign that 16GB of data are showing even if files are shown encrypted?
3. data are also showing on pc, when connected on twrp, but also encrypted.
Any help will be appreciated!
Additionally quite important question: at this state (possible soft brick + encrypted files), is there a chance that if I make a backup to MicroSd card of all the data and then take it our to reinstall rooted stock version of my android that later puting backup in will show my files that were backuped? Could ir be so that phone luckiliy decrypt them itself because it is the same phone? Hope this is clear what I mean.
OK, hopefully all is not lost.
First things first, be REALLY careful. If you start applying factory images, wiping things and generally messing about, if you don't know what you're doing you're putting your data in a lot of danger - Huawei devices do things in weird ways, so be super sure you know the consequences of what you're doing.
Now that's out of the way... it sounds like you haven't done anything to wipe the data. Also, you've already previously unlocked the bootloader which should put you in a good situation. You need to discount TWRP as a potential solution - there is no working decryption for TWRP yet on the Kirin 960 devices and from conversations I've had, it doesn't sound like that is imminent.
What it sounds like has happened is that messing about with root has messed up something on your system partition. Which should be fixable!
As a first step, this is what I'd do.
- Check which version your phone is on if you don't know already (you should be able to find this in ' /version/special_cust/VTR-L09/hw/eu/prop/local.prop')
- Find a full dload zip for the appropriate version (use FirmwareFinder if needed)
- Download the zip an extract the dload app
- Use splitupdate to split the images out of the dload
- Boot the device to bootloader ('adb reboot bootloader' or power on with cable connected and volume down pressed) then do 'fastboot flash system SYSTEM.img'
- Flash BOOT.img too
- Try booting
Hopefully this will fix it, but at the very least it'll get your system partition back to a stock state.
Let me know how it goes. Good luck!
P
First up - Let me say that the complete credit to the method goes to two members here as in the thread https://forum.xda-developers.com/galaxy-tab/help/galaxy-tab-active-2-forum-question-t3712591
BUT BUT BUT what the two experts have missed out is on explaining a clear step by step guide for a complete noob like me . So this is an attempt to explain every step. My tab had root in less than 10 mins .
why i needed the root ?
16gb is not enough for the tab so i wanted to apps and data to be moved to the sd card .
Here are the steps
On the Pc
1. Download the stock firmware (must be the same as in your tab) from samfirmware or any other source.
2. Extract the firmware and the extract archive called AP... . Once extracted you will have a boot.img file in it.
On the TAB
3. Activate developer options by clicking the software version 5 times.
4. In the developer options check OEM unlock and USB debugging
5. Download Magisk Manager v16 from xda and install on the TAB.
Connect the tab to the pc
6. Copy the boot.img file from pc to the tab.
7. Run Magisk Manager and in settings choose the output format as odin compatible tar,
8. Click the INSTALL button in the MAGISK manager and choose 'patch boot image file'
9. After a few minutes a dark screen will appear will read all ok boot image patched...now copy that patched_boot.img.tar file from the tab to the PC and rename it as boot.img.tar
On the Tab
10. Recheck under developer options if check OEM UNLOCK and USB DEBUGG
11. DELETE the GOOGLE account (crucial)
12. Switch of the tab
13. Go to download mode by holding vol down, menu and power together , once asked press vol up to go to the download mode.
14. Connect tab to PC.
On the PC
15. Download ODIN and once downloaded right click and run as administrator.
16. Choose AP and select the previously patched boot.img.tar file.
17. Click START
On the TAB
18. It will run the download and restart , restart will say "VERIFICATION FAILED and aask to RESET and erase .
19. CLICK RESET
20. wait for reset saying ERASING and let the tab restart.
NOW the next step is the most crucial one and it is where i got stuck as none of the members who have rooted their device mention it. I did all of the above procedures repeatedly and failed to get root until i realized there was one FINAL CRUCIAL STEP before enjoying the root.
LAST STEP
ON THE TAB
After the TAB restarts , fill in the initial details (google , samsung account, wifi etc) and before you do anything else INSTALL THE MAGISK MANAGER V16 app you downloaded from XDA .......thats it ....you have root access now . ENJOY!
How did you install Magisk?
When I open Magisk Manager v5.6.4, I get a "Magisk is not installed" and I only have the settings option.
No "install" options.
I have the same tablet. don't know of any twrp that can work with it, therefore leaving me with Magisk Manager only.
Id' be glad to get some help
Thanks,
SOLVED: You must have a functioning network interface in order for the "install" button to appear and you need internet connection to "install the v16 zip".
Magisk is OpenSource though, right? so probably it can be changed to allow offline installation as well.
Rooteed
Well Crap...I just got my Nice, New, Sparkleing Tab Active2 and cant root it yet. I have the New US version SM-T397U Unlocked model. cant find a Stock firmware on Sammobile as of yet...any ideas?
EDIT: Neeeevermind... I did a lil hacking and cracking (for about 26min, lol) to find the files I needed for the SM-T397U. If anyone is looking for em let me know and I'll shoot em' your way. Guessing I'm the first person to root a T397U, hope more will follow. I havent even had this thing 6 hours yet. Thanks for the write up and all those that contributed to the tools and info!
I followed every steps till the end and everything went smoothly. But once I rebooted the tablet, I got the red label on the top left corner: "custom binary blocked by OEM lock". The tablet won't boot properly anymore "OEM unlock" was enabled in the Developers options, I double checked to be sure before flashing.
Edit:
Actually, the "custom binary blocked by OEM lock" appears as soon as I modify the system partition (I wanted to modify the Generic.kl in the keylayout folder on the system partition). If you do not touch anything, everything is fine.
[X-POST from here ]
Worked perfectly, Thank you very much!
WARNING: THIS WILL WIPE EVERYTHING ON YOUR TABLET.
Backup all of your important files before you flash the patched boot.img using odin.
I tried to backup my app data using samsung switch and it worked, but didn't restore most of my device settings and all of my app data.
(Good thing I kept backups for my important apps that had in app backup functionality - like Nova launcher and Squid)
Keep in mind that you probably won't be able to get OTA updates after you perform these steps, it doesn't matter though since this tablet isn't going to be updated that frequently (The 8.0 update is going to come at the end of 2018, source)
Hello.
I tried this but when i using the magisk manager i have an error meassage and the following log:
- Copying image to cache
- Device platform: armeabi-v7a
- Existing zip found
1038+1 records in
1038+1 records out
1063528 bytes transferred in 0.022 secs (48342181 bytes/sec)
- Unpacking boot image
MagiskBoot v18.1(18100) (by topjohnwu)
- Boot Image Modification Tool
mmap failed with 12: Out of memory
! Unable to unpack boot image
! Installation failed
Can you help what i did wrong?
Thank you
oem unlock does not appear
SOLUTION FOUND
how do you oem unlock
I have wasted hours on this, waited weeks, tried the date trick with a legit setup, but the oem unlock never appears, running oldest version of firmware 7.1.1 feb 2018, what gives?
Tried reinstalling firmware via odin, successful flash but no factory reset. Suspect this made no difference. Got the security fail on PIT error, needed a new version of odin and selecting individual AP etc. files fixed this.
apparently you need a samsung or google account
So trying a samsung account... no dice
Now trying adding a sim card as well... success
OK after months of waiting and trying things, this just worked!
Update- I lost the date trick, have to wait 7 days after step 7 on auto date, just appears in developer options no need to press manual update.
https://forum.xda-developers.com/galaxy-s8+/how-to/guide-how-to-skip-rmm-prenormal-install-t3749468
- try downloading UK rom which was released before december '17 (october)
See if it lets the below process work again?
0/ install sim card (was not even the original carrier one in my case although my phone is not carrier locked)
1/ factory reset
2/ on reboot skip all accounts, do not enter a name do not turn on wifi, accept minimal amounts of things
3/ set date to 1/4/19 - turn off automatic date
4/ turn off automatic software updates
5/ enable developer options and turn off auto update system
6/ turn on wifi (date changes)
6b/ change date back
7/ Install samsung account (I went to samsung cloud) (date not changed but software update now triggered despite not touching manual update)
8/ (for interest look at manually check for software updates - it already says 1/4/19 last checked)
9/ reboot
10/ (date is now changed back to today again without my permission)
11/ (it pops up asking to install an update, despite auto updates turned off. - LATER)
12/ (last checked software date is now today (because I left wifi on I think through a reboot) this is 4/5/19 over 1 month later)
13/ go to developer options for the 27868745# time
OEM UNLOCK APPEARED HOLY ****
It is between Bluetooth HCI snoop log and Running services on the dev page, top of the developer options
Since the RMM prenormal thing triggered I had to do this again, so the above instructions do work.
If you stuff up the date just factory reset and start again. Reflash not required
I used a brand new throwaway samsung account for this but thats possibly up to you.
RMM state prenormal
OK now that I've jumped through hoops, installed TWRP
I go to reboot and it's locked recovery again - repeat above OEM unlock reappearing act steps fixes RMM=prenormal. Now it's official again.
Apparently you need to install an RMM patch as well which is not mentioned in this thread.
https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
So, odin -> ap -> TWRP download
quickly press power-up-home when it resets!!!
recovery is not seandroid enforcing appears and TWRP starts.
1. back up all partitions to microsd!
2. install
a TWRP -> magisk
b TWRP -> RMM disabler - this writes to /system defeating the purpose of magisk???
wipe cache/dalvik reboot
on boot:
"Verification failed"
"Unable to restart your device the integrity verification has failed.... erase all your data"
Well recovery boots this time not an RMM error thats nice... oh it runs a few commands and automatically restarts again.
"Verification failed..."
I guess that is a boot loop then, thanks TWRP for not stopping at a menu ffs.
Reflash TWRP with odin, now it halts at TWRP menu.
https://forum.xda-developers.com/ga...t/how-to-recover-verification-failed-t3775722
Apparently I should put in download mode and cancel - Result = fail & TWRP bootloop -> reinstall TWRP
unmountable /data partition - yep thats me - could try format to exfat - ext4 - Result = Verification failed ffs
---------- Post added at 01:52 PM ---------- Previous post was at 01:00 PM ----------
Take 3
"Looks like you didnt flash encryption breaker." no-verity-no-encrypt_ashyx.zip or no-verity-opt-encrypt-6.0 zip well duh of course but which one for t395
https://www.androidinfotech.com/no-verity-opt-encrypt-versions/
seems a few up to 6.0
BTW if you don't press reset and instead try and reboot into recovery you don't have to reflash TWRP
Verification FAIL.
https://forum.xda-developers.com/galaxy-note-8/how-to/guide-how-to-root-device-encryption-t3742493
Take 4 - try reinstating boot.img with no mods.
Try flashing stock AP -> twrp -> DMM fix -> magisk in quick succession & booting tablet
Verification Failed! Reset
Goes to recovery - less errors on TWRP (no mount errors like before) but verification failed again.
Because TWRP is installed I don't get the erasing screen as described by OP....? TWRP does something very quickly I think it says formatting cache, it is doing a standard factory reset. Trying manual factory reset with TWRP does not work.
So I think I need TWRP to prevent DMM tripping and install magisk but I need stock recovery to avoid the verification failing constantly.
Or a new version of TWRP that supports encryption? 3230+ I have 3230...?
Try Stock RO system - twrp - dm verity - magisk
Verification failed. Reset - no dmm error thats nice. TWRP did some extra stuff.
Verification failed again.
#&%^&^#%$#[email protected]#%[email protected]#%#$%
Option 556
Install dmverity patch using stock recovery.
Gives error can't find /misc partition - pretty sure these are TWRP zips only.
Magisk website says install TWRP so I can't see how to avoid TWRP and this annoying verification fail. Maybe try an older version of magisk???
Verification bootloop FIX:?
I tried booting stock, it says something like data corrupt on start, looks the same as the verification failed but with the different message. I let it erase/factory reset with stock recovery.
DMM preload did not trigger on this!
As soon as it succeeded I installed TWRP in case DMM triggers.
Now with fixed data partition (presumably) retry TWRP
1. no verity patch (6.0)
2. magisk
cannot install DMM as it alters system partition...?
No cache wipe.
Lets see what happens...... Black screen but this time
'encryption failed' reset. Press reset.... TWRP does a factory reset
'encryption failed'
LOL now I have an encryption failed bootloop.
Reinstall stock and use stock factory reset again - boot to recovery straight away, wipe data & cache
Now install TWRP (not booted once yet)
Install verity patch 6.0
install magisk 19.1
Boot system for the first time. - got a bootloop? no just taking it's sweet time. Fingers crossed!
Android is starting... WELCOME
HOLY **** IT WORKED
DMM patch not installed and it hasn't tripped DMM yet (the old 7 day wait issue)
SUMMARY:
1/ ensure DMM is official and not preload, OEM unlocked etc with above post steps
2/ flash stock AP - do NOT boot system yet
3/ stock recovery - wipe data and cache
4/ download odin mode - install twrp-3.2.3.0-gtactive2lte-7.1.2.tar
5/ twrp - install no-verity-opt-encrypt-6.0.zip
6/ twrp - install magisk 19.1
7/ Boot system for the first time
So I have not installed RMM patch (system untouched) but I did install the no encryption/dm verity patch.
It actually boots now.... will update if further problems
Interestingly OEM unlock has disappeared, so RMM must be prenormal so it will probably die on reboot. Argh. But everything is restoring OK for now. See what happens...
Magisk app auto installed and passes safetynet. Preserve force enctyption and AVB 2.0/dm-verity unchecked.
Annoyingly despite backing up all my messages to samsung they are not restoring past 20 april. Not the end of the world.
Skype keeps stopping.
Reboot and YES only officially released binaries are allowed to be flashed boot loop.
So lets do this again!
SUMMARY:
1/ ensure DMM is official and not preload, OEM unlocked etc with above post steps
8skip 2/ flash stock AP - do NOT boot system yet
8skip 3/ stock recovery - wipe data and cache
4/ download odin mode - install twrp-3.2.3.0-gtactive2lte-7.1.2.tar
5/ twrp - install no-verity-opt-encrypt-6.0.zip
6/ twrp - install magisk 19.1
7/ Boot system for the second time
Pretty sure I already tried this so it won't work. &^%#@&^$#$#%#$%@##%@
Oh great it has managed to install the update and now the date fix doesn't work. &^#%&^#$#@$%@#$
After waiting 7 days
1/ Use stock recovery factory reset, then immediately hold down-home-power download mode
2/ Odin TWRP, then immediately hold up-home-power to enter TWRP
2a/ TWRP swipe to allow modifications (for RMM patch)
3/ TWRP install RMM patch
4/ TWRP install no verity patch
5/ TWRP install latest Magisk
NB Magisk seems to install itself as an app - its just there.
...Safetynet pass despite RMM editing /system phew
Hello,
With the last version of Magisk, we no longer have the setting to choose the output format as odin compatible tar.
How can we deal with this, please ?
Regards,
Driss35 said:
Hello,
With the last version of Magisk, we no longer have the setting to choose the output format as odin compatible tar.
How can we deal with this, please ?
Regards,
Click to expand...
Click to collapse
You don't have to choose any file type. Magisk scans files automatically.
Also, if your file type is ".lz4", you have to change it to ".img". Unless, you can't continue.
@Drnms thanks for this thread. But, some places have to be updated because of new Magisk versions.
Did App data remain after rooting
Drnms said:
First up - Let me say that the complete credit to the method goes to two members here as in the thread https://forum.xda-developers.com/galaxy-tab/help/galaxy-tab-active-2-forum-question-t3712591
BUT BUT BUT what the two experts have missed out is on explaining a clear step by step guide for a complete noob like me . So this is an attempt to explain every step. My tab had root in less than 10 mins .
why i needed the root ?
16gb is not enough for the tab so i wanted to apps and data to be moved to the sd card .
Here are the steps
On the Pc
1. Download the stock firmware (must be the same as in your tab) from samfirmware or any other source.
2. Extract the firmware and the extract archive called AP... . Once extracted you will have a boot.img file in it.
On the TAB
3. Activate developer options by clicking the software version 5 times.
4. In the developer options check OEM unlock and USB debugging
5. Download Magisk Manager v16 from xda and install on the TAB.
Connect the tab to the pc
6. Copy the boot.img file from pc to the tab.
7. Run Magisk Manager and in settings choose the output format as odin compatible tar,
8. Click the INSTALL button in the MAGISK manager and choose 'patch boot image file'
9. After a few minutes a dark screen will appear will read all ok boot image patched...now copy that patched_boot.img.tar file from the tab to the PC and rename it as boot.img.tar
On the Tab
10. Recheck under developer options if check OEM UNLOCK and USB DEBUGG
11. DELETE the GOOGLE account (crucial)
12. Switch of the tab
13. Go to download mode by holding vol down, menu and power together , once asked press vol up to go to the download mode.
14. Connect tab to PC.
On the PC
15. Download ODIN and once downloaded right click and run as administrator.
16. Choose AP and select the previously patched boot.img.tar file.
17. Click START
On the TAB
18. It will run the download and restart , restart will say "VERIFICATION FAILED and aask to RESET and erase .
19. CLICK RESET
20. wait for reset saying ERASING and let the tab restart.
NOW the next step is the most crucial one and it is where i got stuck as none of the members who have rooted their device mention it. I did all of the above procedures repeatedly and failed to get root until i realized there was one FINAL CRUCIAL STEP before enjoying the root.
LAST STEP
ON THE TAB
After the TAB restarts , fill in the initial details (google , samsung account, wifi etc) and before you do anything else INSTALL THE MAGISK MANAGER V16 app you downloaded from XDA .......thats it ....you have root access now . ENJOY!
Click to expand...
Click to collapse
Hi Dmms,
Please confirm if the data remained (i.e. was not erased) after the rooting?
Thanks in advance.
Hi, in case it is still relevant:
- Tab does a factory reset when booting first time after the boot img is flashed, data on the device is lost. Data on the SD card is not affected
- In my case, flashing boot.img with Odin didn't work. Odin said success, but no root. Heimdall worked fine, tab was rooted at first attempt
Does this guide also work for Android 9 ?
Edit: So it works with Android 9 also but I had to unpack the boot.img with 7zip ZS according to this post https://forum.xda-developers.com/t/samsung-a40-how-to-root.3929496/post-79902328
and re-pack it with normal 7zip according to these steps:
Do you have the boot.img.lz4 file to boot.img unpacked?
You have renamed the magisk_patched.img to boot.img?
You used the normal 7zip to package into a .tar file? Not the 7zZs?
You used the normal Odin 3.14?
Hello, did you manage to remove the "format as internal" lock?
Hi guys,
Trying to root this tablet, when I load the patched magisk file in Odin and perform the download. The tablet restarts and loads like normal but the tablet isn't rooted.
Any ideas?
alguma fortma?
A/A & Welcome,
READ THE FULL GUIDE OR YOU CAN LAND IN TROUBLE
Ain't gonna work on pie official
AND DO PRESS THE THANKS BUTTON
Disclaimer
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or anything that happens to your device
INTRO
This is a full guide for unlock/relock, install TWRP, Root your device and backup/restore stock OS. Each and every step is explained thoroughly with pictures and videos.
I have ASUS Zenfone Max Pro M1 (6GB variant) (X00TD) (ZB601KL), so I can’t test for other variants. Please report back issues, corrections, omissions, etc., though the guide should work for all devices.
THINGS TO KNOW (IMPORTANT)
~Every text written in double quotes “” means the same written without the quotes.
e.g.:- “abcd” means abcd
“zxcv” means zxcv
They (“”) help to separate usual text from the other text (like a command, file name, etc.)
~If you have not enabled file name extensions then you will see files without their extension and vice versa
e.g.:- “filename”, “mypicture” in 1st case
“filename.extension”, “mypicture.png” in 2nd case, respectively.
~Boot Partition or Bootloader:-This is the partition that enables the phone to boot. Without this partition, the device will not be able to boot.
~Recovery Partition:-Recovery partition lets you boots the device into a recovery mode to perform recovery tasks.
~TWRP: - stands for TeamWin Recovery Project. It is a custom touch recovery that is GUI based.
~Flashing: - simplest: - installing
~Fastboot Partition: - lets us reflash partitions. (On device)
~Fastboot: - is an executable used to reflash partitions. It comes with the Android SDK. (On PC)
~Rooting: - an Android phone lets owner edit system files. Thus enabling various tweaks and use of apps that require root access.
~Device driver: - determines how PC will communicate with a device.
~Unlocking/Relocking:-With a locked Bootloader, booting into custom things is not allowed is not. Unlocking lets us do so.
~Reboot: - Switching ON AND OFF (in simple terms)
Requirements
MIND, PC, USB Cable, Internet, Fully charged PC (Windows OS), and obviously Asus Zenfone Max Pro M1
The Real Steps From Here
FOLLOWING THIS GUIDE YOU WILL PROBABLY LOSE ALL THE DATA ON YOUR PHONE SO MAKE A BACKUP FIRST (Don’t worry it’s in guide too)
STEP 1. Downloading all the necessary files
a. Here are 2 zip file with everything you will probably need following the guide :-
basic zip
extension zip
. I have tested the procedures using these files only so maybe other versions might not work. A “guide.doc” with the same text as in here (on XDA) is also present. It will be of great help if you don’t have internet connection in PC.
The basic zip file contains minium files needed.
The extension zip file contains the TWRP recovery(then one used in the guide),guide.docx ,and the videos used here too.
Copy the twrp file to unlock folder of extracted folder.
b. Extract the zip file above.
First download the zip file and Copy to PC
Then Right Click on it
Then click “Extract All”
Uncheck “Show extracted files…”
Click on “Extract”
The folder “zip” will be extracted
Done
This “zip” folder will be called extracted folder in the guide video link to extract zip
To download most up to date version of the files go to links present at last
STEP 2. BACKUP
a. Use an apk backup tool to backup app installers
VIDEO TO BACKUP APP INSTALLERS
b. Some APPS like Whatsapp, etc. have backup to drive function use that
VIDEO TO BACKUP WHATSAPP CHATS
c. Backup SMS AND Call Logs
VIDEO TO BACKUP CALL LOGS AND MESSAGES
d. Copy each and every file from you internal storage to PC.
Video to backup each file to pc
DONE
Step 3. UNLOCKING BOOTLOADER(Data will be wiped)
2 options:-
A. Official Method (NOT TESTED): -
In extracted folder go to “unlock” folder then “Official” folder. Install the “UnlockTool_9.1.0.3_180621_fulldpi_signed_ZB601KL.apk” in Asus and follow the steps from there.
B. Unofficial Method (Tested):-
a. Installing Drivers
Connect phone using USB cable to PC
Right click on This Pc
Go to “Manage” > “Device Manager” Or Just search for “Computer Management”/“Device Manager”
A list will appear.
Find your device (best way to do so is by disconnecting/connecting the device and notice the changes accordingly in the list)
Now right click on it>”Update Driver Software”>“Browse my computer for driver software”
Now either enter path of the driver folder or click on browse and navigate to the driver path from there.
Press Next OR
“Let me pick …”>and select the driver
video to install driver
The drivers have been installed
b. Booting into FASTBOOT
Switch Off the Phone
Hold the Volume UP and Power ON Button Simultaneously
Device buttons labbled image
You will see this on your phone
image of FASTBOOT screen
c. Unlocking Bootloader
Now connect phone using USB cable to PC
Look for the “unlock” folder in the extracted folder.
Open it
Find “unlock.cmd” or “unlock” file
(Or “unlock no erase.cmd” to keep data {not tested})
Open it
Done
d. You will see some messages in yellow/brown/white colour on your phone
You will most probably see “encrypting your device”, “warning Bootloader unlocked” messages, let phone do its work and don’t interrupt it, and keep cable connected. Phone might reboot too. The phone will at last boot into stock OS and you will see the device setup screen.
image of the warning message
e. Now if you wanted TO ONLY UNLOCK BOOTLOADER THEN THE JOB IS DONE, long press power button. If you want to root or flash TWRP then continue (Tested method to root requires TWRP flashing or you can try the untested method to root only)
Step4. Installing/Flashing TWRP
TESTED METHOD
a. Connect phone using USB cable to PC
b. Don’t setup your device just now because possibilities are you might lose the data again
c. Boot into fastboot mode
d. Open the “unlock” folder in the extracted folder.
Now Two Different ways to opt for from here:-
i. THE LAZY METHOD (Tested)
a. Open “flash_recovery.bat” or “flash_recovery” in the “unlock” folder of the extracted folder.
b. You can flash the tested or any other recovery using this script.
c. Follow the steps from the script
video of how to use the script
d.Then go to step of Flashing ZIPS of The Manual Method
e. Done
OR
ii. The Manual Method (Tested)
a. Keeping Shift Key pressed, right click {with mouse} in the blank white space of the “unlock” folder’s explorer window.
b. From the menu select “open command window here”
c. A CMD window will be opened
open cmd video
d. Now type “fastboot devices”
e. See if your device is connected. You will see something like this
f. Now type “fastboot flash recovery twrp-3.2.3-0-X00TD-20181024.img”
If you want to flash any other recovery instead of “twrp-3.2.3-0-X00TD-20181024.img” write the file name of your recovery file. Make sure it’s in “unlock folder”. Though this recovery is the only tested one (by me).
g. Now keeping the phone connected to PC, boot into TWRP/Recovery by pressing the Volume Down and Power ON Button Simultaneously.
h. The usual warnings, messages and recovery boot screen will flash:-
warning image
twrp flash screen image
i. It may take some time to load so wait for at least 2 minutes.
j. Now if touch is not working press power button 2 times (on and off the screen)
video showing how to enable touch in twrp
k. If it shows “Swipe to Unlock” do so. If it shows “Swipe to Allow Modifications” then wait and continue reading …
swipe to allow image
swipe to unlock
l. “Swipe to Allow Modifications” means you allow TWRP to modify system. This will make sure TWRP remains in the phone and not just vanish after a reboot but it also means you will have to flash some other files to be able to boot into stock rom back.
m.
2 ways from here:-
i. Now after swiping, Decrypt Screen will appear just press cancel.
decrypt screen image
OR
ii. If you have data on the device then enter pin/password or try default_password.
If you had kept pattern then either go back and change it or try this:-
1 2 3
4 5 6
7 8 9
these no’s correspond to pattern dots.
Say you kept pattern “third row left to right” then the password is 789 .
If all these fail then you will have to lose your data.
n. As we don’t have any precious data in our phone we will (or you are compromising)
Press “Wipe”
Press “Format Data”
TYPE “yes”
Press “tick” or “enter key”
Done
wipe data video
>Flashing ZIPS
o. Now Copy these 2 files
i. “decrypt.zip” or “decrypt”
ii. “Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip” or “Disable_Dm-Verity_ForceEncrypt_12.16.2018”
From extracted folder to your phones internal storage.
p. Go to Install>select the zip>swipe to flash (flash dm_verity… then decrypt…)
If you don’t see your device storage connected then try reconnecting using USB cable and also check if MTP is enabled.
enable mtp video
>Done
Want to root? Then continue…
or >
Now reboot to system Go to Reboot>System
video to show how to rebbot to system in twrp
Step 5. Rooting
We will be using Magisk to root you can use any other method but this is the only tested method.
a. Copy “Magisk-v18.0.zip” or “Magisk-v18.0” to your phones internal storage from extracted folder.
b. Go to Install>select Magisk…>swipe to flash
Done
c. Now reboot to system Go to Reboot>System
reboot video
e. To use Magisk properly you may need to download latest apk. (Link at last)
Step 6. Relock (NOT TESTED)
a. Connect phone using USB cable to PC
b. Boot into fastboot mode
c. Open “Relock” folder from extracted folder
d. Open “relock.cmd” or “relock” file
Done
Step 7. RESTORING
a. First setup the Device again
b. Copy each and every file back to the phone storage
c. Now to restore messages see the restoring part of this video here
d. WhatsApp messages will be automatically restored after you install the app with same number as before.
Tips
After rooting don’t just go on and flash a custom rom. Take a backup first (of all partitions) using TWRP and keep it safe somewhere so you won’t need to find unbrick tutorials later. Plus you will have your most stable and tailored rom with you.
Also don’t just go on and flash xyz mod. Research and then Flash.
Magisk is our best friend. It lets you do modifications without hurting the system. The Magisk modules are most safe mods as they can be reverted back easily.
And don’t just go on and debloat stock OS. In Magisk there is a module called Debloater use that. You can easily revert back if anything goes wrong.
Other good Magisk modules: - Energized, Systemizer, MidnightCore & Advanced Charging Controller (acc) but do read their XDA guides first.
Sources/Credits:-
Dm_Verity.zip Official XDA:-
link
Original unlocking XDA:-
link
Magisk XDA:-
link
Original Decrypt Data XDA:-
link
TWRP Used XDA:-
link
Credits to the authors of the above guides
Plus sorry for bad editing of videos. I am facing some problems. Will try to post better videos.
I thank all the members who have made the previous guides for their hard work. This guide by no means disrespects their hard work. This guide is just an Addition instead of an Alternative.
Read the full guide
Press the thanks button
Re edited the guide.
Added link of apps used in YouTube videos.
Not working for pie official
Deleted cruddy comments. Good job.
Good initiative but not so good noob guide. Please format it for better organization and better understanding.
malikmiran19 said:
2. BACKUP
>Use an apk backup tool to backup app installers
howto video
Click to expand...
Click to collapse
Appreciate the effort . I have a suggestion. It would be helpful to put the name or link of the app that you used to back up apks.(some apk extractor lite ig). I'll provide the one I found anyway. https://www.apkmirror.com/apk/ankit.../apk-extractor-lite-2-8-android-apk-download/
camaroamarelo said:
Good initiative but not so good noob guide. Please format it for better organization and better understanding.
Click to expand...
Click to collapse
Did so
GliderZ said:
Appreciate the effort . I have a suggestion. It would be helpful to put the name or link of the app that you used to back up apks.(some apk extractor lite ig). I'll provide the one I found anyway. https://www.apkmirror.com/apk/ankit.../apk-extractor-lite-2-8-android-apk-download/
Click to expand...
Click to collapse
Added apk links in YouTube videos
Anyone tried unlocking without erasing data?
TheDarkKnight said:
Anyone tried unlocking without erasing data?
Click to expand...
Click to collapse
nyimak
fuzuy said:
nyimak
Click to expand...
Click to collapse
What?
TheDarkKnight said:
What?
Click to expand...
Click to collapse
it means im interested in your question and im following it
I want to unlock bootloader, flash TWRP and flash a custom ROM (Cerberus OS).
I have rooted and flashed TWRP before in my previous device but I'm not familiar with unlocking and Custom ROM.
Do I have to follow all hese steps for what I want to do or I must skip decrypt/encrypt and Magisk?
dharsouparno1 said:
I want to unlock bootloader, flash TWRP and Custom ROM.
Click to expand...
Click to collapse
U can flash twrp then flash ROM and probably flash magisk for root tooo
malikmiran19 said:
U can flash twrp then flash ROM and probably flash magisk for root tooo
Click to expand...
Click to collapse
Thanks for the help.
I'm running into some problems while installing the driver software on my Windows 10 laptop. It shows Error 10 this device cannot start.
I tried to uninstall and reinstall the drivers, rebooted my pc on every step, tried to install while connected to my phone, but nothing seems to work.
I've installed the Pie Beta for Asus Zenfone Max Pro M1 (not sure if this is causing it)
Is there a solution to this problem?
I am currently on Beta Pie...will these methods work for bootloader unlocking and TWRP, custom rom flash ???? I just wanna use PE/Havoc OS rom...no other tweaks or root
thanks its working
I updated to pie beta and I think this guide is not working for that, because when flashing twrp. I'm getting 'request download size is more than allowed size' and I tried every way possible to solve it. But no luck Hope you can help me with it, or maybe it'll work after stable version?
---------- Post added at 04:15 AM ---------- Previous post was at 04:11 AM ----------
utsavdey said:
I am currently on Beta Pie...will these methods work for bootloader unlocking and TWRP, custom rom flash ???? I just wanna use PE/Havoc OS rom...no other tweaks or root
Click to expand...
Click to collapse
It's not working for me. I also updated to pie beta few days back.
Is this method working on pie stable build
Anyone tried this method on the stable pie build 056?
Hello!
So recently I was able to install LineageOS 18.1 (GSI) + GApps on my Samsung Galaxy Tab A 8 (SM-T290) tablet and wanted to share how I did it. I noticed a lack of decent step-by-step guides to modding this tablet so I figure I'd share what I learned through scouring multiple threads and through multiple headaches. Fun fact: I also got this working with LineageOS 19 (GSI), however it ran pretty poorly and Android 12 is ugly as hell so why bother anyway? ALSO interestingly enough, you'll see I wrote [SM-T290N] in the title as well. That is the model of the Kid's Edition of this phone, which happens to be the one I had. So I can confirm this process works for the Kid's Edition of this tablet as well as the original.
Some Things To Note
Below I'll list the software/firmware I used in this process. You don't necessarily need to follow this exactly but I don't see any reason not to. The end result is a working install of LineageOS with GApps so if that's what you want I would just follow along step-by-step. ALSO I'm writing this from memory so if I make a mistake please let me know and I'll try and correct it.
Click to expand...
Click to collapse
What You'll Need
Your tablet
A USB Cable to connect your tablet to your PC
A 4GB+ MicroSD card
A Windows PC
Some patience
Instructions
Preparing Your MicroSD Card
1. Place the LineageOS 18.1 .img file from this thread (On SourceForge, there is a section below the files about the naming conventions and how they relate to the hardware of your device and configuration of your ROM. I used the lineage-18.1-20220315-UNOFFICIAL-arm64_bvS-vndklite.img.xz image for my device. If your device is slightly different, you can use Treble Info to determine what ROM you should use. Just make sure to use the VNDKLITE rom if your device supports it.
2. Place the multidisabler .zip folder on there as well. This will preserve encryption provided by TWRP after rebooting.
3. Finally, place the MindTheGapps .zip folder on your SD card (make sure to get the correct version. In my case this was the 11.00-arm64 version).
4. Insert your MicroSD card into your device.
Unlocking the Bootloader
So the first thing you're gonna want to do is unlock your OEM bootloader on your Samsung device.
1. Go to Settings->About Phone->Software Information and look for a field called "Build Number". Tap this Five Times until you see a notification saying developer settings were enabled.
2. Go to Settings->Developer Settings and look for the setting labeled OEM Unlock and turn it on.
If you don't see this setting try connecting to wifi, changing your date and time to around two months prior (I set mine to back to May 2021 since the firmware I was using was set in July 2021), then go back to your developer settings and switch them off and back on again. You should now see the OEM Unlock option.
Click to expand...
Click to collapse
3. From here, you can reboot your device into Recovery Mode by holding the Vol+ and Vol- buttons when the device begins to boot again.
4. You should see a blue screen with some options. Press the Vol+ button to enter Download Mode. This is where you'll use Odin to flash the firmware you need as well as TWRP.
Flashing Firmware
So when I attempted this process I used Magendanz's Unofficial TWRP 3.6.0 as it is the only version of TWRP I found for this device. I also used Odin v3.14.1_3B Patched from this XDA thread. Magendanz's TWRP requires you to have the T290XXU3CUG4 Firmware (I used the XAR region) in order to flash TWRP to your device (you can check wether or not you already have this firmware on your phone by looking the About Phone section again). It takes a while to download though make sure you have some time.
1. Download Odin and run the program. Unzip your firmware folder and use the relevant files when selecting the BL, AP, CP, CSC fields in Odin. I didn't use the HOME_CSC just leave it blank.
2. Connect your device via USB and Flash this firmware to your device.
3. Once your device restarts, go through the setup process and then repeat the Unlocking the Bootloader instructions above in order to make sure it is unlocked again.
4. Reboot your device the same way as stated above.
Flashing TWRP
Before starting, be aware that after you flash TWRP to your device, your device will restart and attempt to open the stock system again. You're going to want to hold the Power and Vol+ buttons simultaneously. You will likely get a warning screen saying that the bootloader is unlocked and may ask you to do a factory reset, this (I believe) is fine. The key here is that once you press the Power Button to continue (as instructed on the warning screen) you'll want to immediately press and hold the Power and Vol+ keys for around 6 Seconds before letting go again (you should be seeing the Samsung Galaxy Tab A logo screen). After letting go, wait around 3-4 seconds, if nothing changes, restart the device by holding all three buttons (Power, Vol+,Vol-) and attempt the process again. It's a pain in the ass but you'll get it eventually. Just make sure not to let the device boot into the system again as that can cause problems in TWRP and you'll likely have to start the process over (from flashing the firmware).
1. Once your tablet is once again in Download Mode, open Odin again and flash the TWRP (tar.md5 file) to the AP (recovery) partition. Do not use any of the other partitions.
2. If this is successful, your phone will begin to reboot. Quickly press and hold the combination of buttons Power and Vol+ until you see the warning dialog pop up. Once you do, release all buttons and be ready to quickly press and release the Power button continue, and then immediately after press and hold the Power and Vol+ buttons again for 6 seconds. After around 6 seconds, release all buttons. Wait around 3-4 seconds and, if the screen does not change to the TWRP logo, restart the device by pressing and holding all buttons simultaneously and try this step again.
3. If you have entered into TWRP, congrats!
Installing Custom ROM + Software in TWRP
1. The first thing you'll want to do is select the Wipe->Format Data. Type 'yes' and hit enter (or swipe I forget which).
2. Next, select Install, and then select your MicroSD card as your storage device. You should see your zip files (if not switch from the install image option).
3. Install the multidisabler, do not reboot
4. Go back into Install and select Install Image (might not be the exact naming) option. Select your MicroSD card as the storage device again and install the LineageOS 18.1 rom. Do not reboot.
5. Go back into Install and select your MindTheGapps zip file and install it.
Now, a lot of people run into a problem when trying to install Gapps which is your device complaining about no more available space in the system partition. If this is the case, go back to Wipe and select Advanced Wipe. Select your system partition and then select Change or Repair Partition. Once you're here you should see the size and available space of your partition. You'll want to hit Resize Partition and let it do it's thing. To confirm it worked, go back to Wipe->Advanced Wipe->Select System->Change or Repair Partition and your available space should be much larger now. Now just attempt to install MindTheGapps again.
Click to expand...
Click to collapse
Final Steps
Once you reboot you should be able to successfully reach the setup screen for Lineage. Go through the steps of setting up your device as usual and be sure that Gapps are installed. Go ahead and re-enable developer settings and enable USB-Debugging and Root Debugging. The reason for this is that, when I first installed Gapps, Google Play Protect would keep throwing warnings at me about my device not being Google Play Certified. This means I couldn't actually use any of the google play services. If you run into the same issue, here are the steps you can take to fix it:
1. First, go into Settings->Apps and find your Google Play Services app. Clear the cache and delete the app data, then reboot your device. If you try and sign into the Google Play store and you are able to without getting any play protect warnings, then you're good you can disregard the following steps.
2. If you are still receiving these warnings, you'll want to head over to this site and follow the instructions (I'm not gonna tell you how to use ADB here). Once you submit your framework ID, reboot your device. Everything should be working fine now.
And that's it! If I am forgetting any steps please let me know, again I am writing this from memory of the process so it may be missing some minor details. I hope this helps!!!
How's the stability, speed and the responsiveness on Lineage with a t290? I have mine rooted debloated and twrp installed but it is slow on stock OS
kkdamion said:
How's the stability, speed and the responsiveness on Lineage with a t290? I have mine rooted debloated and twrp installed but it is slow on stock OS
Click to expand...
Click to collapse
It runs surprisingly well! Much better than stock. There’s virtually no input lag and the battery life is also very solid on lineage.
Where i run into some lag is when trying to use apps that have embedded video in them. For whatever reason the T290 cannot handle video very well at all.
So yeah I would definitely recommend trying it, it’ll really breathe new life into that tablet
i cant get google play services to work and i cant fetch device_id to register the device
i get "no closing qoute" message
adb shell 'sqlite3 /data/data/com.google.android.gsf/databases/gservices.db \
/system/bin/sh: no closing quote
EDIT: downloaded "android device id" APK from the internet and gathered the framework id information from the app
kkdamion said:
i cant get google play services to work and i cant fetch device_id to register the device
i get "no closing qoute" message
adb shell 'sqlite3 /data/data/com.google.android.gsf/databases/gservices.db \
/system/bin/sh: no closing quote
EDIT: downloaded "android device id" APK from the internet and gathered the framework id information from the app
Click to expand...
Click to collapse
Glad it worked out for you! Let me know if you have any more questions and I'd be happy to help.
Hi! is this applicable also for SM-T295?
for those trying to figure out the Google Play Certified page with the adb command
Code:
adb shell 'sqlite3 /data/data/com.google.android.gsf/databases/gservices.db \
"select * from main where name = \"android_id\";"'
do : adb shell
first then paste in :
sqlite3 /data/data/com.google.android.gsf/databases/gservices.db \
"select * from main where name = \"android_id\";"
and it shouldn't give you the error
i must say. linageos on my sm-t290 is really nice
its fast and smooth way much better then stock fw
i would reccomend anyone with a t290/t295 to install this GSI
Im into a bootloop right now after a few fails with installing Lineage on my SM-T290..
Seems like i cant install any rom? not sure how to fix this issue, can anyone point me in the right direction?
Im able to get into TWRP and download mode. but cant install any rom?
thepalek1ng said:
Hello!
So recently I was able to install LineageOS 18.1 (GSI) + GApps on my Samsung Galaxy Tab A 8 (SM-T290) tablet and wanted to share how I did it. I noticed a lack of decent step-by-step guides to modding this tablet so I figure I'd share what I learned through scouring multiple threads and through multiple headaches. Fun fact: I also got this working with LineageOS 19 (GSI), however it ran pretty poorly and Android 12 is ugly as hell so why bother anyway? ALSO interestingly enough, you'll see I wrote [SM-T290N] in the title as well. That is the model of the Kid's Edition of this phone, which happens to be the one I had. So I can confirm this process works for the Kid's Edition of this tablet as well as the original.
What You'll Need
Your tablet
A USB Cable to connect your tablet to your PC
A 4GB+ MicroSD card
A Windows PC
Some patience
Instructions
Preparing Your MicroSD Card
1. Place the LineageOS 18.1 .img file from this thread (On SourceForge, there is a section below the files about the naming conventions and how they relate to the hardware of your device and configuration of your ROM. I used the lineage-18.1-20220315-UNOFFICIAL-arm64_bvS-vndklite.img.xz image for my device. If your device is slightly different, you can use Treble Info to determine what ROM you should use. Just make sure to use the VNDKLITE rom if your device supports it.
2. Place the multidisabler .zip folder on there as well. This will preserve encryption provided by TWRP after rebooting.
3. Finally, place the MindTheGapps .zip folder on your SD card (make sure to get the correct version. In my case this was the 11.00-arm64 version).
4. Insert your MicroSD card into your device.
Unlocking the Bootloader
So the first thing you're gonna want to do is unlock your OEM bootloader on your Samsung device.
1. Go to Settings->About Phone->Software Information and look for a field called "Build Number". Tap this Five Times until you see a notification saying developer settings were enabled.
2. Go to Settings->Developer Settings and look for the setting labeled OEM Unlock and turn it on.
3. From here, you can reboot your device into Recovery Mode by holding the Vol+ and Vol- buttons when the device begins to boot again.
4. You should see a blue screen with some options. Press the Vol+ button to enter Download Mode. This is where you'll use Odin to flash the firmware you need as well as TWRP.
Flashing Firmware
So when I attempted this process I used Magendanz's Unofficial TWRP 3.6.0 as it is the only version of TWRP I found for this device. I also used Odin v3.14.1_3B Patched from this XDA thread. Magendanz's TWRP requires you to have the T290XXU3CUG4 Firmware (I used the XAR region) in order to flash TWRP to your device (you can check wether or not you already have this firmware on your phone by looking the About Phone section again). It takes a while to download though make sure you have some time.
1. Download Odin and run the program. Unzip your firmware folder and use the relevant files when selecting the BL, AP, CP, CSC fields in Odin. I didn't use the HOME_CSC just leave it blank.
2. Connect your device via USB and Flash this firmware to your device.
3. Once your device restarts, go through the setup process and then repeat the Unlocking the Bootloader instructions above in order to make sure it is unlocked again.
4. Reboot your device the same way as stated above.
Flashing TWRP
Before starting, be aware that after you flash TWRP to your device, your device will restart and attempt to open the stock system again. You're going to want to hold the Power and Vol+ buttons simultaneously. You will likely get a warning screen saying that the bootloader is unlocked and may ask you to do a factory reset, this (I believe) is fine. The key here is that once you press the Power Button to continue (as instructed on the warning screen) you'll want to immediately press and hold the Power and Vol+ keys for around 6 Seconds before letting go again (you should be seeing the Samsung Galaxy Tab A logo screen). After letting go, wait around 3-4 seconds, if nothing changes, restart the device by holding all three buttons (Power, Vol+,Vol-) and attempt the process again. It's a pain in the ass but you'll get it eventually. Just make sure not to let the device boot into the system again as that can cause problems in TWRP and you'll likely have to start the process over (from flashing the firmware).
1. Once your tablet is once again in Download Mode, open Odin again and flash the TWRP (tar.md5 file) to the AP (recovery) partition. Do not use any of the other partitions.
2. If this is successful, your phone will begin to reboot. Quickly press and hold the combination of buttons Power and Vol+ until you see the warning dialog pop up. Once you do, release all buttons and be ready to quickly press and release the Power button continue, and then immediately after press and hold the Power and Vol+ buttons again for 6 seconds. After around 6 seconds, release all buttons. Wait around 3-4 seconds and, if the screen does not change to the TWRP logo, restart the device by pressing and holding all buttons simultaneously and try this step again.
3. If you have entered into TWRP, congrats!
Installing Custom ROM + Software in TWRP
1. The first thing you'll want to do is select the Wipe->Format Data. Type 'yes' and hit enter (or swipe I forget which).
2. Next, select Install, and then select your MicroSD card as your storage device. You should see your zip files (if not switch from the install image option).
3. Install the multidisabler, do not reboot
4. Go back into Install and select Install Image (might not be the exact naming) option. Select your MicroSD card as the storage device again and install the LineageOS 18.1 rom. Do not reboot.
5. Go back into Install and select your MindTheGapps zip file and install it.
Final Steps
Once you reboot you should be able to successfully reach the setup screen for Lineage. Go through the steps of setting up your device as usual and be sure that Gapps are installed. Go ahead and re-enable developer settings and enable USB-Debugging and Root Debugging. The reason for this is that, when I first installed Gapps, Google Play Protect would keep throwing warnings at me about my device not being Google Play Certified. This means I couldn't actually use any of the google play services. If you run into the same issue, here are the steps you can take to fix it:
1. First, go into Settings->Apps and find your Google Play Services app. Clear the cache and delete the app data, then reboot your device. If you try and sign into the Google Play store and you are able to without getting any play protect warnings, then you're good you can disregard the following steps.
2. If you are still receiving these warnings, you'll want to head over to this site and follow the instructions (I'm not gonna tell you how to use ADB here). Once you submit your framework ID, reboot your device. Everything should be working fine now.
And that's it! If I am forgetting any steps please let me know, again I am writing this from memory of the process so it may be missing some minor details. I hope this helps!!!
Click to expand...
Click to collapse
bro, I have a problem, my tablet is in a bootloop and I don't know what to do, try with other custom roms but it's the same, what do I have to do so that when I install a custom room it doesn't give me that error?
Flashing the Gapps package resulted in an error: Failure to mount '/system_root' (Invalid argument)
V0latyle said:
Flashing the Gapps package resulted in an error: Failure to mount '/system_root' (Invalid argument)
Click to expand...
Click to collapse
Sorry for the bother, new to Android modding scene.
I went into the recovery menu (oem unlock on) and tried to flash TWRP as written on this guide, but I get a secure check fail : aboot on my device and fail on Odin. What do I do here?
Edit: Aparently my device is SM-T295, basically the LTE version of the same device, which is why it isn't recognising it. My bad.
Do you have any video to teach better ???
HyruleanKnight said:
Sorry for the bother, new to Android modding scene.
I went into the recovery menu (oem unlock on) and tried to flash TWRP as written on this guide, but I get a secure check fail : aboot on my device and fail on Odin. What do I do here?
Edit: Aparently my device is SM-T295, basically the LTE version of the same device, which is why it isn't recognising it. My bad.
Click to expand...
Click to collapse
Shouldn't matter, TWRP is the same for both variants.
There's two ways to get around the secure check fail problem:
After updating via Odin, make sure you immediately interrupt the boot and force reboot into Download Mode. Then, flash TWRP.
Or, after updating, allow your device to boot to Android, skip through the setup wizard (make sure you connect to the internet), and enable Developer Options. Ensure OEM Unlocking is there and grayed out. If not, leave it for a bit until it is. This disables Vaultkeeper on the bootloader. Then, reboot to download mode and flash TWRP.
In both cases, after flashing TWRP, DO NOT let the device boot into Android. Force boot into recovery, then install the Multidisabler from here.
Now to my own problem...
I don't know what I did differently (or wrong) but I cannot get LineageOS to boot correctly on my T290. I was running 18.1 before. I recently updated to CVG3 and followed the same process as I did before - flashed TWRP, then installed the LineageOS GSI to /system.
18.1 continuously bootloops without even loading LineageOS.
19.1 gets to the LineageOS splash screen, and occasionally the setup screen, but continuously reboots also.
After flashing TWRP, I'm installing the multidisabler, then wiping /system, /data, /cache.
Any idea what I'm doing wrong?
@J.Michael any thoughts? You're more familiar with Samsung than I am
V0latyle said:
Shouldn't matter, TWRP is the same for both variants.
There's two ways to get around the secure check fail problem:
After updating via Odin, make sure you immediately interrupt the boot and force reboot into Download Mode. Then, flash TWRP.
Or, after updating, allow your device to boot to Android, skip through the setup wizard (make sure you connect to the internet), and enable Developer Options. Ensure OEM Unlocking is there and grayed out. If not, leave it for a bit until it is. This disables Vaultkeeper on the bootloader. Then, reboot to download mode and flash TWRP.
In both cases, after flashing TWRP, DO NOT let the device boot into Android. Force boot into recovery, then install the Multidisabler from here.
Now to my own problem...
I don't know what I did differently (or wrong) but I cannot get LineageOS to boot correctly on my T290. I was running 18.1 before. I recently updated to CVG3 and followed the same process as I did before - flashed TWRP, then installed the LineageOS GSI to /system.
18.1 continuously bootloops without even loading LineageOS.
19.1 gets to the LineageOS splash screen, and occasionally the setup screen, but continuously reboots also.
After flashing TWRP, I'm installing the multidisabler, then wiping /system, /data, /cache.
Any idea what I'm doing wrong?
@J.Michael any thoughts? You're more familiar with Samsung than I am
Click to expand...
Click to collapse
I think I have a solution.
I see that you are installing the multidisabler after you booted TWRP and by wiping the partitions, however, what you are supposed to do is this:
After you have booted into TWRP and have swiped to allow modifications, go to Wipe> Format Data and type yes. Don't reboot, and don't wipe any other partitions.
After that, go to install and then install the multidisabler, don't reboot.
Then install the latest LineageOS gsi to the system partition, and finally install gapps, then reboot.
Make sure you are choosing the arm64_bvS_vndklite variant, otherwise it will bootloop.
Hope this helps!
Just Mike said:
I think I have a solution.
I see that you are installing the multidisabler after you booted TWRP and by wiping the partitions, however, what you are supposed to do is this:
After you have booted into TWRP and have swiped to allow modifications, go to Wipe> Format Data and type yes. Don't reboot, and don't wipe any other partitions.
After that, go to install and then install the multidisabler, don't reboot.
Then install the latest LineageOS gsi to the system partition, and finally install gapps, then reboot.
Make sure you are choosing the arm64_bvS_vndklite variant, otherwise it will bootloop.
Hope this helps!
Click to expand...
Click to collapse
Okay, so install Multidisabler AFTER wiping data. I'll try that.
I'm using the bgS image so it's already got Google apps. I didn't have any success flashing any of the Gapps packages on the vanilla images.
Is Multidisabler still necessary on Android 11 on this device, or do we just need a patched vbmeta.img?
V0latyle said:
Okay, so install Multidisabler AFTER wiping data. I'll try that.
I'm using the bgS image so it's already got Google apps. I didn't have any success flashing any of the Gapps packages on the vanilla images.
Is Multidisabler still necessary on Android 11 on this device, or do we just need a patched vbmeta.img?
Click to expand...
Click to collapse
Yes, Multidisabler is necessary, otherwise it'll bootloop. I haven't tried anything with a patched vbmeta and frankly don't want to.
The bgS version will work just fine for Android 11.
Currently running Android 13 with LineageOS 20.0, the bvS version. Gotta say it works great. MindtheGapps 13 will work, I haven't encountered any "This device is not certified" issues.
Just Mike said:
Yes, Multidisabler is necessary, otherwise it'll bootloop. I haven't tried anything with a patched vbmeta and frankly don't want to.
The bgS version will work just fine for Android 11.
Currently running Android 13 with LineageOS 20.0, the bvS version. Gotta say it works great. MindtheGapps 13 will work, I haven't encountered any "This device is not certified" issues.
Click to expand...
Click to collapse
Do I need to wipe /system or /boot or anything before installing? I did exactly as you said - rebooted to recovery (was running Samsung stock), formatted data, installed multidisabler, then installed a LineageOS 19 image to /system. It begins to boot (LineageOS animation) then reboots.
Are you using Andy Yan's builds?
V0latyle said:
Do I need to wipe /system or /boot or anything before installing? I did exactly as you said - rebooted to recovery (was running Samsung stock), formatted data, installed multidisabler, then installed a LineageOS 19 image to /system. It begins to boot (LineageOS animation) then reboots.
Are you using Andy Yan's builds?
Click to expand...
Click to collapse
Nope, you don't have to wipe any other partitions, only format data
Yes, I'm using Andy Yan's builds. I'll link the thread here: https://forum.xda-developers.com/t/gsi-13-lineageos-20-trebledroid-based.4517345/
If I may ask, which type GSI from Andy Yan did you use?
Just Mike said:
Nope, you don't have to wipe any other partitions, only format data
Yes, I'm using Andy Yan's builds. I'll link the thread here: https://forum.xda-developers.com/t/gsi-13-lineageos-20-trebledroid-based.4517345/
If I may ask, which type GSI from Andy Yan did you use?
Click to expand...
Click to collapse
Trying to get back into TWRP, just a sec...
-arm64_bgS.img
Flashing the vndklite one now to see if it works
If I can get this working, I plan on using a bgN flavor so I can just install Magisk, since I don't use SuperSU
Edit: vndklite is bootlooping too