This version of TWRP works on the Lenovo TB-X606FA, TB-X606F and TB-X606X.
Warning: this TWRP will not work for any of the Tab M10 variants with Qualcomm SOCs. For the TB-X505F, see this thread. For the TB-X605F/L, 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.
*/
Encryption
This device was released with Android 9 using full disk encryption (FDE). But we now have Android 13 GSIs for this tablet - and Android 13 does not support FDE. Android 13 only supports file-based encryption (FBE).
If you are using a ROM/GSI that uses FBE, you must use the twrp with -fbe in the name. If you use the wrong one, twrp will not be able to decrypt the data partition.
If you don't know if you're using FBE or FDE, then run this command while Android is running: adb shell getprop ro.crypto.type. If it returns "block", then your device is FDE. If it returns "file", it's FBE.
Installation
With a stock ROM, it is recommended that you also install Magisk. This will ensure TWRP remains your default recovery.
If Windows 10/11 does not recognise your tablet in fastboot mode, then see post #2.
Step-by-step guide
download TWRP to your PC (see the Download section below)
download the latest magisk.apk to your SDcard or OTG device. Change the filetype from "apk" to "zip".
get a copy of the vbmeta.img file from the stock ROM. It should be located in one of the subdirectories of LMSA's c:\ProgramData\LMSA\Download\RomFiles directory (after you download it using the LMSA rescue (power-off mode). This is only required the first time you flash TWRP, or the first time after you re-flash the whole stock ROM.
if your bootloader is already unlocked, go to step 5. 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 flashing unlock
follow the instructions on the tablet, then reboot to Android.
note: if fastboot reports <waiting for device>, then you need to install the Mediatek USB drivers. Go to developer.android.com/studio/run/oem-usb, then find the link to Mediatek (MTK) and follow the installation instructions.
note: after unlocking, tablet will take a while to come back up - because it has to do a factory reset and encrypt data again.
flash the TWRP image:
Code:
adb reboot bootloader
fastboot flash recovery twrp_X606FA_11.img
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot reboot recovery
backup the stock boot, system and vendor partitions in TWRP, if you don't have backups already
load 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:
2023-03-27 - add TWRP 3.7.0 for FBE ROMs/GSIs (Android 13+) only
2022-02-06 - added separate download for TB-X606F
2021-12-16 - TWRP 3.6.0 updates
- support for Android 12 decryption (keymaster)
2021-07-05 - TWRP 3.5.2 updates
- corrected display of Cyrillic (and other non-ASCII characters) in file names on external drives (utf8)
2021-03-10 - TWRP 3.5.1 updates
- cherrypicked update 1995 to force splash screen to display on boot
- orientation is now landscape (for tablets)
- updated install instructions to reflect new Magisk apk (v22).
2021-02-02 - fix blank screen on boot - don't need to press power button anymore to wake screen up
2021-01-24 - TWRP 3.5.0_10-0: initial release
Downloads (FDE)
This will work with stock ROMs and most pre-A13 ROMs/GSIs.
TWRP 3.6.0_11-0 for X606FA: twrp-X606FA_11.img
TWRP 3.6.0_11-0 for X606F: twrp-X606F_11.img
Downloads (FBE)
This will not work with stock ROMs or most pre-A13 ROMs/GSIs. This is for ROMs/GSIs that use FBE to encrypt. Android 13+ only supports FBE.
TWRP 3.7.0_12-1 for X606FA with FBE encryption: twrp-X606F_12.1.fbe.img
Source code
https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp/tree/twrp-12.1
https://github.com/Yahoo-Mike/recovery_device_lenovo_X606FA/tree/android-12.1-fbe
Credits
The guys at TeamWin Recovery Project.
Everyone whose device trees I plagiarised from GitHub.
Contributors
Yahoo Mike
Created 2021-01-24
Last Updated 2023-03-27 (FBE support)
Windows 10/11 does not recognise tablet in fastboot mode
If your tablet is recognised by ADB but not by fastboot in Windows, you might need to get the latest versions of fastboot and the Mediatek usb drivers.
1. use the latest fastboot version
Make sure you are using the latest version of fastboot. There were major changes to fastboot for Android 10.
If you are using PowerShell, make sure it's picking up the fastboot you expect: fastboot --version. If not, use ./fastboot from the directory with the executable.
2. update device drivers
Try the latest Mediatek (MTK) drivers from Install OEM USB drivers. When they are loaded, they appear in Device Manager as "Kedacom USB Device/Android ADB Interface".
If Windows complains that the drivers are unsigned and refuses to load them, then do this as Administrator in Windows:
bcdedit /set testsigning on
reboot Windows
install the drivers
bcdedit /set testsigning off
In Windows 11, you might also need to turn off Secure Boot in your PC's BIOS to get the bcdedit command to work.
So I have the ZA5W0097US, would you suggest this wouldn't work?
ldeveraux said:
So I have the ZA5W0097US, would you suggest this wouldn't work?
Click to expand...
Click to collapse
That looks like a TB_X606F. This TWRP might work. We won't know for sure until someone tries.
Remember, the screen will be blank when TWRP boots up. You'll just have to click the power button twice to wake it up. I'll try and fix that over the next few days.
If you decide to try this TWRP and it doesn't work, please let me know what happens. And when you're booted into Android, can you tell me what the results of these ADB commands are?
Code:
adb shell getprop ro.hardware
adb shell getprop ro.boot.hardware
New version is now available in the first post.
The blank screen issue is mostly fixed...mostly. The screen is still blank on boot when decrypting data, but then it wakes up. No need to press the power button anymore.
I just got my TB-X606F (it's actually finishing setup right now) and I'm going to try flashing this TWRP onto it. I *think* the only difference between the "F" and "FA" version is that the "FA" comes with some sort of Alexa capability.
Both adb commands output "mt8768".
TB-X606F/ZA5T0300US (the manual also says TB-X606X) confirmed TWRP and Magisk are working. Had a hell of a time with getting fastboot to work on my main machine so I used a virtual machine to do everything with fastboot.
sirp0p0 said:
TB-X606F/ZA5T0300US (the manual also says TB-X606X) confirmed TWRP and Magisk are working. Had a hell of a time with getting fastboot to work on my main machine so I used a virtual machine to do everything with fastboot.
Click to expand...
Click to collapse
Cool. I'll update the OP.
Maybe check you have the latest version of fastboot on your main machine. There were some major changes for Android 10.
Good call. My adb and fastboot were both way out of date.
I also have the TB-X606F and was able to get this working 100%. I thought it was going to wipe my system so I backed everything up beforehand, but no wipe. Just replaced recovery with TWRP and here I am. Thanks a ton, great to have another TWRP recovery device!
ldeveraux said:
... I thought it was going to wipe my system so I backed everything up beforehand, but no wipe.
Click to expand...
Click to collapse
It will only wipe if you are unlocking the bootloader for the first time.
Thanks for the feedback.
Tried this process and ran into an issue. Flashed TWRP Okay, flash vbmeta ok, rebooted to twrp, but could not find magisk on sdcard for some reason. Not tablet won't take fastboot commands. Says waiting for device
adb device shows the tablet
snickle said:
Tried this process and ran into an issue. Flashed TWRP Okay, flash vbmeta ok, rebooted to twrp, but could not find magisk on sdcard for some reason. Not tablet won't take fastboot commands. Says waiting for device
adb device shows the tablet
Click to expand...
Click to collapse
Rebooteed to bootloader flashed twrp and vbmenta. REbooted to recovery and twrp came up. Installed magisk zip and rebooted. No root and stock recovery comes up instaead of TWRP.
THoughts?
Also still no fastboot commands available when tablet booted, just from bootloader.
Tried completely reflashing stock image, still no change.
snickle said:
...rebooted to twrp, but could not find magisk on sdcard for some reason.
Click to expand...
Click to collapse
You have to download Magisk-v21.4.zip and push it to /external_sd/.
If you did that, can you see your other files in /external_sd/ ?
snickle said:
...tablet won't take fastboot commands. Says waiting for device
adb device shows the tablet
Click to expand...
Click to collapse
Make sure you have the latest adb and fastboot from Google. There were some major changes to fastboot for Android 10.
Also make sure you have the latest USB drivers from Lenovo.
I have the latest adb and drivers. fastboot commands used to work.
I rebooted to bootloader and flashed thre patched boot image made with the canary version of magisk and got root.
I then reflashed twrp and vbmeta and things seem to be working. Except for fastboot commands whlle booted.
snickle said:
I have the latest adb and drivers. fastboot commands used to work.
Click to expand...
Click to collapse
For Windows, the latest fastboot --version is 31.0.0-7110759
snickle said:
...things seem to be working. Except for fastboot commands whlle booted.
Click to expand...
Click to collapse
If you are using Windows 10, check that the "Android Bootloader Interface" driver is loaded in Device Manager when the tablet is in fastboot mode. See this post.
And when you say "except for fastboot commands while booted", do you mean "while the tablet is booted in fastboot mode" or "while the tablet is booted in twrp recovery or Android system"?
Yahoo Mike said:
For Windows, the latest fastboot --version is 31.0.0-7110759
If you are using Windows 10, check that the "Android Bootloader Interface" driver is loaded in Device Manager when the tablet is in fastboot mode. See this post.
And when you say "except for fastboot commands while booted", do you mean "while the tablet is booted in fastboot mode" or "while the tablet is booted in twrp recovery or Android system"?
Click to expand...
Click to collapse
Latest ADB and drivers loaded.
Fastboot commands work while in fastboot mode, but do not work when booted to system any more.
snickle said:
Fastboot commands work while in fastboot mode, but do not work when booted to system any more.
Click to expand...
Click to collapse
That's ok. That's how it's supposed to work.
ADB only works when your device is in recovery or system. It won't work when you're in fastboot or EDL mode.
Fastboot only works when your device is in fastboot mode. It won't work when you're in EDL, recovery or system.
The fastboot utility is an interface to the Android bootloader. When your device is in fastboot mode, you can use this utility to configure (some of) the bootloader and partition images. That's about it. I'm oversimplifying again, but...once the bootloader has passed on execution to EDL or a kernel (recovery or system), the fastboot utility can't work because the bootloader process is no longer running.
Unhelpfully fastboot just displays the "waiting for device" message, rather than something like "waiting for device to enter fastboot mode".
I hope that helps explain what's going on.
Twrp is working as expected no issues I have found, except for the need to press the power button s few times after booting into recovery to get twrp screen.
Hello! I need a bit of help... I have a TB-606F, 4GB/64GB version
I'm stuck on step 5. I've unlocked the bootloader, flashing TWRP and vbmeta seems successful, but then I cannot reboot into recovery. Using the fastboot reboot command I get "fastboot: usage: unknown reboot target recovery". If I try to reboot using volume up + volume down + power it eventually boots to Android.
Any thoughts are much appreciated!
Related
It's a bit urgent to get solved, I'm at college, and that's the only way to talk with my parents, being 1 or 2 days without answering them would be a problem, since they will start to get worried.
Phone: Motorola Moto G 2014, XT1063
Using Team Win Recovery Project v2.8.0.1
Basically I was trying to update to the Android 5.0, since I had my phone rooted, I decided to go with an customized ROM.
DIdn't understand why, but it f**ed up.
Basically I cleaned everything, and in an act of desperation I also lost my sdcard, I've been trying to install the ROM through sideload, but it's not working, I get the error *failed to write data protocol fault no status*, and the phone keeps rebooting, and stuck in the "WARNING BOOTLOADER UNLOCKED"
I appreciate any kind of help, as I said, it's really important to solve this ASAP.
Thanks in advance!
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck
gouzzz said:
Basically I was trying to update to the Android 5.0, since I had my phone rooted, I decided to go with an customized ROM.
Click to expand...
Click to collapse
1) download TWRP 2.8.4.0 and install it through fastboot.
2) Since you have no sdcard we will use the mtp capability of twrp
-- Boot into your newly installed recovery. Check the version
-- Go to Mount and disable mtp and unmount everything. Now enable mtp. You should see that Data is mounting automatically and should appear on your Computer.
-- Transfer your ROM (I recommend The Titan Prime Rom for XT1063/64. It's based on stock and much more polished than CM12)
-- Download and transfer pa-gapps (MICRO MODULAR PACKAGE).
-- Download and transfer latest SuperSU (min version 2.45 is required by our device).
-- Wipe Dalvik, Cache, System and Data
-- Now Flash ROM, GApps and SuperSU. reboot and wait. it will take a couple of minutes.
Doppel u r right. follow doppel steps.
doppelhelix said:
1) download TWRP 2.8.4.0 and install it through fastboot.
2) Since you have no sdcard we will use the mtp capability of twrp
-- Boot into your newly installed recovery. Check the version
-- Go to Mount and disable mtp and unmount everything. Now enable mtp. You should see that Data is mounting automatically and should appear on your Computer.
-- Transfer your ROM (I recommend The Titan Prime Rom for XT1063/64. It's based on stock and much more polished than CM12)
-- Download and transfer pa-gapps (MICRO MODULAR PACKAGE).
-- Download and transfer latest SuperSU (min version 2.45 is required by our device).
-- Wipe Dalvik, Cache, System and Data
-- Now Flash ROM, GApps and SuperSU. reboot and wait. it will take a couple of minutes.
Click to expand...
Click to collapse
The device appear as offline in the fastboot, sometimes even doesn't appear, where can I get the drivers?
I searched for naked versions, and "universal" ones, but none seems to work.
gouzzz said:
The device appear as offline in the fastboot, sometimes even doesn't appear, where can I get the drivers?
I searched for naked versions, and "universal" ones, but none seems to work.
Click to expand...
Click to collapse
You can get Motorola drivers here. You probably also need a recent version of adb and fastboot. You can ge it here Minimal ADB and Fastboot. Install it.
start "Minimal ADB and Fastboot" by navigating to the Start Menu Folder you choose to create during installation or the desktop shortcut you choose to create and select "Minimal ADB and Fastboot"
You should now see a command window open.
Put your device in fastboot mode and connect usb.
Now just do verify type this command
Code:
fastboot devices
the output should show something like this (your number is different)
Code:
fastboot devices
ZX1D225X69 fastboot
now put your recovery.img into the directory where your command window is open and start flashing
Code:
fastboot flash recovery NAME_OF_RECOVERY.img
---------- Post added at 15:34 ---------- Previous post was at 15:31 ----------
gouzzz said:
EDIT: Now it doesn't charge, or something. I connected it to charge, but it keeps appearing 0% for more than 30 minutes, I can't even access the menu from "Volume Down + Power On"
Click to expand...
Click to collapse
You need a wall charger. USB from pc does not supply enough power. And you need at least 25% (ish) otherwise fastboot will refuse do do anything.
doppelhelix said:
You can get Motorola drivers here. You probably also need a recent version of adb and fastboot. You can ge it here Minimal ADB and Fastboot. Install it.
start "Minimal ADB and Fastboot" by navigating to the Start Menu Folder you choose to create during installation or the desktop shortcut you choose to create and select "Minimal ADB and Fastboot"
You should now see a command window open.
Put your device in fastboot mode and connect usb.
Now just do verify type this command
Code:
fastboot devices
the output should show something like this (your number is different)
Code:
fastboot devices
ZX1D225X69 fastboot
now put your recovery.img into the directory where your command window is open and start flashing
Code:
fastboot flash recovery NAME_OF_RECOVERY.img
---------- Post added at 15:34 ---------- Previous post was at 15:31 ----------
You need a wall charger. USB from pc does not supply enough power. And you need at least 25% (ish) otherwise fastboot will refuse do do anything.
Click to expand...
Click to collapse
On the MOUNT and UNMOUNT processing I don't see anything on my PC, I don't even know how to unmount it. It only appears Enable MTP and disable.
How am I supposed to load the ROMS?
Tried with sideload but got an errror : "Error executing updater binary in zip .."
Seems like the drivers aren't working properly, I have Windows 8.1, on the site it doesn't talk about it, this might be the problem? Cause I instaled motorola device manager, I scan for drivers but it doens't find anything, and the phone apperas with the yellow triangle on the Device Manager.
----------------------------------------------------------------------------
----------------------------------------------------------------------------
EDIT: I managed to boot the Titan 5.0.2, but now it's stuck in the 4 balls moving around, i waited for about 1hour.
Hi,
I updated my good old Kindle Fire HD 7 (tate) to cm 12.1 and because of problems with the Play store I made a factory reset. Since then it is in a bootloop showing only the blue teamwin screen with some flickering about every 5-6 seconds.
As I read here (http://forums.androidcentral.com/sa...p-after-factory-reset-cyanogenmod-12-1-a.html), I need to use fastboot.exe to start a new recovery but... fastboot does not recognize the device.
What is working?
adb status-window shows
...Android Debug Bridge
State: unknown (or recovery)
adb reboot revovery - reboots the device
adb reboot bootloader - reboots the device showing a "fastboot logo"
fastboot devices
< waiting for device > / or just no reaction
fastboot -i 0x1949 getvar product
TATE-PUT-08
Okay, after some research I updated my driver (as seen here http://forum.xda-developers.com/showthread.php?t=2271909) and they seem to be installed properly but nothing changes to the behaviour shown above.
What to do?
And thanks a lot!
My systems: Windows 7 Professional 64 bit or Windows 7 Home Premium 64 Bit
..getting creative, I tried
fastboot -i0x1949 boot philz_touch_6.48.4-tate.img
creating boot image...
creating boot image - 8343552 bytes
downloading 'boot.img'...
OKAY [ 2.817s]
booting...
OKAY [ -0.000s]
finished. total time: 2.817s
..and it reboots into the same teamwin splash screen boot loop
...with adb status-window saying "recovery"
Ok, I had the courage to flash and tate is working again:
1. adb reboot bootloader (then in Fastboot mode)
2. fastboot -i0x1949 flash recovery philz_touch_6.48.4-tate.img
3. fastboot -i0x1949 boot philz_touch_6.48.4-tate.img
4. two reboots and cm 12.1 is working
Same problem! PLEASE HELP!
I'm stuck with THE EXACT same problem.
Please tell me how to go about this step-by-step?
I hope you reply asap..
TIA.
Diplominformatiker said:
Ok, I had the courage to flash and tate is working again:
1. adb reboot bootloader (then in Fastboot mode)
2. fastboot -i0x1949 flash recovery philz_touch_6.48.4-tate.img
3. fastboot -i0x1949 boot philz_touch_6.48.4-tate.img
4. two reboots and cm 12.1 is working
Click to expand...
Click to collapse
can you please do a step by step write-up please?
1. start windows command prompt (cmd.exe) in Administrator Mode
2. type "adb reboot bootloader"
3. type "fastboot -i0x1949 flash recovery philz_touch_6.48.4-tate.img"
4. type "fastboot -i0x1949 boot philz_touch_6.48.4-tate.img"
reboot (perhaps several times)
preparations (if not yet done):
- install Android development kit or download adb somewhere
- download philz_touch_6.48.4-tate.img, copy to same folder as adb
- connect kindle via usb
Good Luck
Diplominformatiker said:
1. start windows command prompt (cmd.exe) in Administrator Mode
2. type "adb reboot bootloader"
3. type "fastboot -i0x1949 flash recovery philz_touch_6.48.4-tate.img"
4. type "fastboot -i0x1949 boot philz_touch_6.48.4-tate.img"
reboot (perhaps several times)
preparations (if not yet done):
- install Android development kit or download adb somewhere
- download philz_touch_6.48.4-tate.img, copy to same folder as adb
- connect kindle via usb
Good Luck
Click to expand...
Click to collapse
I bricked my kindle by using FireFlash to get into recovery, and I didn't check the box for the bootloader. Now I am stuck in a boot loop. Every time I use a command in adb, it says it can't find a device. I have tried with a factory cable and with a regular USB. I tried updating the driver through the Device Manager, but it can't find a driver for my kindle. I found a few drivers to choose from on a website (I would post the link, but it won't let me), but none of them seemed to work. Is there something I am doing wrong?
whether the tablet says fastboot or teamwin, it will not start fastboot -i0x1949 flash recovery philz_touch_6.48.4-tate.img, it will just say waiting for device...
hiii
Same situation , no solution until now
unimoose said:
I bricked my kindle by using FireFlash to get into recovery, and I didn't check the box for the bootloader. Now I am stuck in a boot loop. Every time I use a command in adb, it says it can't find a device. I have tried with a factory cable and with a regular USB. I tried updating the driver through the Device Manager, but it can't find a driver for my kindle. I found a few drivers to choose from on a website (I would post the link, but it won't let me), but none of them seemed to work. Is there something I am doing wrong?
Click to expand...
Click to collapse
In device managment, set to see the hidden devices, must appear as TATE-PVT-8, depending the version of Windows you're using must set the signed drivers to disable.
Then update the driver to tate with this controllers.
And use fatbootmode, can use: KFHD_SRTool_v1.2 to revert to completly stock.
Hopes works for you.
Enomaly said:
whether the tablet says fastboot or teamwin, it will not start fastboot -i0x1949 flash recovery philz_touch_6.48.4-tate.img, it will just say waiting for device...
Click to expand...
Click to collapse
Are you saying that the above mentioned method will not work? So what is the possible solution?
This thread is intended to get a fully working twrp for our new device sooner than later by more of us participating.
This is a testing thread so YES ANYTHING CAN GO WRONG. But most likely will not go wrong..
All test builds compiled by me are from @mauronofrio source code
https://github.com/mauronofrio/android_device_oneplus_guacamole_TWRP
This guide was copied and pasted from @mauronofrio Twrp thread.
Install guide:
Actually seems "fastboot boot twrp.img" is not working so we need to use another guide:
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Now you should check which slot are you using with this command "fastboot getvar current-slot"
5. Now you should change the slot in use with this command "fastboot --set-active=*" you should replace with the slot is not in use, for example if you are using slot a the command will be "fastboot --set-active=b"
6. Now you should flash the twrp in the boot partion using this command "fastboot flash boot twrp.img"
7. Now reboot the device with in recovery mode scrolling the menu with the volume button and selecting "Recovery Mode" with the power button
8. First thing go in reboot menu and restore the old active slot
9. Now you can flash the installer (Actually you can do it using sideload, start sideload server from twrp advanced menu and from pc use this command "adb sideload twrpinstaller.zip")
If you are already rooted, you can skip all and directly flash the installer like a magisk module. Always remember that after you flashed the installer you will be unrooted.
Tips:
If you alread have a twrp flashed you can only flash the new installer zip or the new installation method to update your TWRP (remember to flash again magisk or your system will not boot).
If you have some problems with backup, like 255 error or something similar please check this guide: https://forum.xda-developers.com/one...e-999-t3801632
For the Bacups use always "system_image" and "vendor_image" instead of "system" and "vendor".
I need the following logs in order to find issues.
start a terminal window and enter below commands to get the logs
When TWRP boots enter below commands in terminal:
Code:
adb shell "getprop" > getprop.txt
adb pull /tmp/recovery.log
adb shell "dmesg" > dmesg.log
adb logcat > logcat.txt
and post the files here.
Links will be in post #2
Links to test builds
Test-0.2 f2fs filesystem
Twrp.img https://www.androidfilehost.com/?fid=1395089523397969888
Twrp installer https://www.androidfilehost.com/?fid=1395089523397969887
Test-0. 3 ext4 filesystem
Twrp.img https://www.androidfilehost.com/?fid=1395089523397969903
Installer https://www.androidfilehost.com/?fid=1395089523397969902
Under 6. Should we be using "fastboot flash recovery xxx.xxx" or the one from the post?
I might be able to test evening today.
Sent from my GM1911 using Tapatalk
vickyjusme said:
Under 6. Should we be using "fastboot flash recovery xxx.xxx" or the one from the post?
I might be able to test evening today.
Sent from my GM1911 using Tapatalk
Click to expand...
Click to collapse
fastboot flash boot twrp-test.img
Tried this method, but TWRP does not load. Stuck on this (image attached)
Reboot sticks to this screen again. Cannot access fastboot from here, but I can see my device from adb devices. Help me?
https://imgur.com/1s6dejl
Edit: start by power on+volume down loads fastboot.. Phew...
vukis said:
Tried this method, but TWRP does not load. Stuck on this (image attached)
Reboot sticks to this screen again. Cannot access fastboot from here, but I can see my device from adb devices. Help me?
https://imgur.com/1s6dejl
Edit: start by power on+volume down loads fastboot.. Phew...
Click to expand...
Click to collapse
Where are the logs. Please don't test and not provide logs. But thanks for informing test 0.3 doesn't work.
Just wondering how long you waited.
Foolproof method to install roms, twrp + root.
Read through the directions first before you start anything and your phone wont get bricked. Even if it does, you can use the msm tool guide that I linked below to restore it and get it prepped up for custom rom install again.
Pre-requisites:
1) Update to latest android 11 through software update.
2)Have oneplus drivers and adb/fastboot drivers installed
[TOOL]Minimal ADB and Fastboot [2-9-18]
Introduction ADB and Fastboot are arguably two of the most indispensable tools used when working with Android devices. If you really want to modify, debug, and tweak along with their countless uses in rooting, and other procedures ADB and...
forum.xda-developers.com
Download TWRP unofficial for oneplus 7 pro android 11 here and move it into minimal adb and fastboot folder
[RECOVERY] [12] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
3a)Download Magisk v23.0 if you want root
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
3b) Move custom rom into internal storage like download folder for custom rom install
if you have issues with fastboot not recognizing device or other driver issues, click this link https://www.droidwin.com/fix-android-device-not-showing-in-fastboot-mode/
*****Extra Steps Required for T-mobile variant for installing custom roms****
-I tried everything and couldnt get havoc os to install on my t-mobile variant. It would always end up in a bricked state. To get around this, you first need to convert it to international following this guide then follow steps below after you have kept updating it in system until there are no more updates available. https://forum.xda-developers.com/t/guide-how-to-convert-tmobile-op7-to-international.3935947/
Guide for installing custom rom over android 11
-unlock bootloader and enable usb debugging then connect phone- use this video on how to unlock bootloader but dont follow his other steps yet
-open up cmd in minimal adb and fastboot folder and type in adb devices and make sure phone shows up
-in cmd, type in "adb reboot bootloader"
-in cmd, type in "fastboot devices" and make sure phone shows up
-in cmd, type in fastboot boot "name of your twrp file"
It should boot into twrp. at this point, you should have your rom zip file in the internal storage
-install the custom rom.zip. In my case, i installed havoc 4.8. After thats done, go back to wipe and format data. For extra measures, go to wipe and advanced wipe and wipe dalvik cache, data and vendor then reboot.
-to get root, set up the phone and enable usb debugging again. Transfer magisk v23.0 to download. adb reboot bootloader and go into recovery if your rom has one(havoc has its own) or fastboot into twrp again and install magisk. At this point, you can also install twrp if you want. Follow the guide above to install the unofficial twrp.
Guide for installing TWRP and root on official android 11
-unlock bootloader and enable usb debugging then connect phone- use the video above on how to unlock bootloader but dont follow his other steps for twrp yet
-open up cmd in minimal adb and fastboot folder and type in adb devices and make sure phone shows up
-in cmd, type in "adb reboot bootloader"
-in cmd, type in "fastboot devices" and make sure phone shows up
-in cmd, type in fastboot boot "name of your twrp file"
It should boot into twrp. at this point, you should have magisk v23.0zip in your internal storage like in download folder if you want root
-go to advanced then flash current twrp
-then install magisk v23.0 and you're done
Hi all,
Haven't seen a guide for this and thought I would write one for myself and others
DISCLAIMER* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
You will also lose any L3 Widevine DRM Certification, aka no more HD netflix. Please keep this in mind.
REQUIREMENTS:
SDK Platform-tools (Get it here)
Getting boot.img
Download Lenovo Rescue and Smart assistant.
Link: https://support.lenovo.com/au/en/downloads/ds101291-rescue-and-smart-assistant-lmsa
You'll need a lenovo ID, Sign in or register an account
and once there go to "Rescue" > Tablet Rescue
Input your serial number > Make sure it finds the tablet > Click Start Rescue to download the firmware
The download is about 2.6GB
Navigate to
Code:
C:\ProgramData\RSA\Download\RomFiles\YT_J706F_S000049_211204_ROW
Which should have the firmware and boot.img
LET'S BEGIN!
Extract the SDK Platform tools folder to an easily accessible directory
UNLOCKING THE BOOTLOADERNOTE: THIS WILL ERASE ALL DATA FROM YOUR DEVICE SO MAKE SURE TO TAKE A BACKUP IF NECESSARY
Extract the SDK Platform tools folder to an easily accessible directory
Go to Settings > About Tablet > Tap build number 7 times. Go back to main page of Settings > System > Developer options and enable OEM unlocking and USB Debugging
Reboot the system to bootloader (Press Vol - and Power key or type "adb reboot bootloader" by opening a command prompt window in Platform tools directory)
To unlock bootloader run the command
Bash:
fastboot flashing unlock
The device will do a factory reset and restart itself
After Setting up your device install the magisk app from GitHub. I recommend Magisk-v24.3 as that's what worked for me.
Link: https://github.com/topjohnwu/Magisk/releases
ROOTING [MAGISK] - Using Fastboot
Transfer your boot.img to Internal Storage
You can use the command:
Bash:
adb push .\boot.img /storage/emulated/0/
After installing the magisk app Go to Install > Select and Patch a File
Select the boot.img you transferred to Internal Storage. Magisk will patch your boot.img and display the output folder after the process.
Transfer the Patched boot.img to your computer and rename it to boot_patched.img
Bash:
adb pull /storage/emulated/0/Download/magisk_patched-[random_text].img
Reboot to Bootloader
Bash:
adb reboot bootloader
Flash the patched image
Code:
fastboot flash boot boot_patched.img
You also need to flash vbmeta.img. This file is available in the firmware folder.
Bash:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
Reboot the device by typing
Code:
fastboot reboot
Check Magisk manager and the device must be rooted now
TroubleshootingBoot loop after flashing magiskCould be a variety of things. Make sure that:
You've flashed vbmeta.img
You're using v24.3 of magisk
To get back to a working stage you can flash the stock boot.img and vbmeta.img. To enter fastboot mode just hold Vol - (Vol Down) + Power button forever until the fastboot mode text appears on the screen.
fastboot not detecting deviceYou'll have to install a driver manually from device manager.
Install a driver already on this computer
Select Android Phone
Select Google
Select Android ADB composite driver
After that fastboot could recognise my tablet
ThanksJohannj22 For the guide on another version of lenovo tablet which I followed https://forum.xda-developers.com/t/...of-lenovo-yoga-smart-tab-and-root-it.4387131/
Ofc Magisk for the ability to root so easily.
One of my first posts, sorry if there's any mistakes and let me know if there's any. There wasn't a forum for the yoga tab 11 so I posted here. I've been looking for months on how to root and I'm glad I figured it out and this post is here for others.
After typing flashing unlock command it enters fasboot mode and nothing happens, Left it for a while and nothing changed.
If I remember correctly it printed something on the fast boot screen when it started and when it's done. Then I rebooted into android to verify that it was actually wiped.
Hi,
about loosing L3 widevine, i assume this will also loose Amazone Prime HD, correct?
Also, will L3 Dome Back If i Go Back top Stock? Or are there any known workarounds to geht IT Back?
Noob Questions i assume, sorry, but maybe you can clarify
Ender
Tablet new, first rooted, thx. for manual!