Related
I just decided to move to CM12.1 on my Droid Turbo (XT1254) after the 1/27 Snapshot (YOG7DAO3J1) was posted. I am running this with TWRP 2.8.7.0, BHB27 Kernel, and OpenGAPPS 5.1. So far, almost everything has been fantastic and the performance of the device is like night and day compared to the Verizon software.
My problem is that the CM12.1 ROM has my device encrypted to begin with, which is nice but giving me trouble. I can't get into TWRP to install Xposed framework or other .zips via ADB. I have tried the following:
Disabling require password on startup
Changing the password in Android
Changing the password from root ADB shell
Using a pin
Trying "default_password"
Can anyone give me a solution or some advice? Any help is greatly appreciated!
Having same issue with TWRP not recognizing any decryption password given... Any ideas out there? Is TWRP incompatible with Droid Turbo HW Encryption, or ?
P_6 said:
Having same issue with TWRP not recognizing any decryption password given... Any ideas out there? Is TWRP incompatible with Droid Turbo HW Encryption, or ?
Click to expand...
Click to collapse
This thread is kinda old and I assumed nobody really knew what was going on with it either. I ended up just not using the encryption. The first time around mine was encrypted without me knowing, which was the issue. I just wiped all partitions and flashed the ROM again...
I am having a similar issue so i thought i would chime in, despite the older thread. I had a stock ROM that was encrypted and I was able to unlock and root with SunShine fine. Flashed on TWRP 2.8.7 and ran into a "Unable to mount storage. Failed to decrypt data" error. Updated to TWRP 3.0.0 and still have the same issue. Still working through a resolution as the phone is still functional if I just boot normally. When you mentioned you wiped all partitions, what process did you use? If i can just get access to the interal storage I can flash a ROM and be good to go.
Asyt said:
I am having a similar issue so i thought i would chime in, despite the older thread. I had a stock ROM that was encrypted and I was able to unlock and root with SunShine fine. Flashed on TWRP 2.8.7 and ran into a "Unable to mount storage. Failed to decrypt data" error. Updated to TWRP 3.0.0 and still have the same issue. Still working through a resolution as the phone is still functional if I just boot normally. When you mentioned you wiped all partitions, what process did you use? If i can just get access to the interal storage I can flash a ROM and be good to go.
Click to expand...
Click to collapse
So far, the only way I have been able to get encryption working with CM12.1 on the Droid Turbo is to do the folllowing (Note: This assumes you have bootloader unlocked and TWRP installed as your recovery):
Part 0: Make sure you have what you need
1. Stock Droid Turbo Firmware SU4TL for your device
2. The version of CyanogenMod 12.1 that you need. I recommend a Snapshot, but it's up to you.
3. TWRP 3.0.0 or later for your Droid Turbo.
Part 1: Final set up (Yes, we do this first)
1. Download CM12.1 & Download OpenGapps arm for 5.1
2. Wipe device (system, data, cache, internal storage), copy CM12 install zip and opengapps install zip via USB to device.
3. Flash CM12 and OpenGapps in TWRP
4. Set up device how you want it to be (install your apps, set up your accounts, etc).
5. Set whatever lock-screen PIN / Password / Pattern you are going to want on your phone in general!
6. Make a Nandroid backup of your 100% set up phone in TWRP
7. Copy your backup TWRP folder to your PC.
Part 2: Encrypt device and put everything back how we want it.
1. Flash stock Verizon firmware (SU4TL) via Fastboot. Do not flash stock Recovery, but put back TWRP if you did somehow (I use a simple bash script I have attached below).
2. Boot device, go through initial set up, don't download apps (we're going to be wiping the device soon).
3. Make sure your battery is 80%+ charged, and your device is plugged in.
4. Set a password or PIN on your phone.
5. Encrypt your device (this will be fairly fast, as /data is empty, but you should be asked for your encryption password on boot.)
6. Reboot to recovery. TWRP will ask you for your password to decrypt. It should work with no problem.
7. Copy your backed-up TWRP folder with your CM12 install to your device via USB. The TWRP folder goes in the Internal Storage root directory.
8. Still in TWRP (Do not reboot), go to Restore, and select the backup you just copied over. This will replace the stock rom with your CM12 backup.
9. Your CM12 install will be restored, but your device will remain Encrypted.
10. Reboot into CM12. Win.
You will need to decrypt your device every boot with the password that you selected when you initially encrypted your device. Your lock-screen password CAN BE DIFFERENT. That is why I do it this way. I have a fairly long password to decrypt my device on boot-up, but a pattern as my lock screen. That way I can quickly get into my phone during daily use without having to constantly type in a fairly complicated password.
Team Win Recovery Project
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
Read more about TWRP here: https://twrp.me/about/
DOWNLOAD:
1) Install the TWRP app from the Play Store or grab the apk from our website
2) Open the app, agree to the terms, and enable root access
3) Select TWRP Flash
4) Search for your device and select the version you wish to download
5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
OR:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.
FEATURES:
FBE Decryption support
MTP support
ADB root
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
CONTRIBUTIONS:
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
TWRP for Mi 6, Tool/Utility for the Xiaomi Mi 6
Contributors
TheStrix
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Created 2017-06-10
Last Updated 2018-07-07
FAQ
FAQ:
HOW DO I GET LOGS SO WHEN I COMPLAIN I'M NOT COMPLETELY IGNORED OR SHAMED BY OTHER USERS?
To get logs while in TWRP, you should connect your device to your PC and use adb.
adb pull /tmp/recovery.log
adb exec-out dmesg > dmesg.log
This will create 2 files in the directory your shell is currently in, recovery.log and dmesg.log. You will need to upload these somewhere such as a pastebin or Google Drive. You can also attach it to your XDA post (recommended!)
If you are having an operating system boot issue, you should gather a ramoops log instead. Do this while in TWRP after the failed boot:
adb exec-out "tar c /sys/fs/pstore 2>/dev/null" > pstore.tar
MY RECOVERY KEEP GETTING REPLACED WITH STOCK RECOVERY... WHAT KIND OF MAGIC IS THIS?
The file: /system/bin/install-recovery.sh present in stock system is responsible for that.
You can simply stop this from happening by deleting it or renaming it to install-recovery.sh.bak using any root explorer or via TWRP (Advanced -> File Manager).
Reserved
Nice
Praying for good developers working on Mi6
Thx for TWRP
thanks
Thanks a lot for your work.
Any comparison to ValoXis / cofface version?
Thanks
Thanks a lot for your work!
Can I disable dm-verify with this revovery when using official MIUI rom?
Can not be backed up
.nice thank you !
Maybe lineage is next ? ?
Any reason why it asks me for a password?
Thanks!
Yeah, Parth its here
Now it's time to xiaomi to release kernel sources
Successfully re-flashed from ValoXis version via official TWRP app.
Thanks Strix!
Tried to restore from backup, This is the thing what I backed up :
1. Backup1 : boot, recovery, EFS
2. Backup2 : system, system image, data, cache
I tried to restore from backup2 first from failing the installation of China dev ROM. Wipe system, data, cache, dalvik, and do the backup.
It's booted okay (it uses the custom boot animation I picked), but at the end / near the end of the boot animation, there's low battery sound played, then the device is switched off.
Tried again to wipe everything, restore backup2, then backup1, I got the same "low battery" sound notification.
In the end I had to reflash Xiaomi.eu ROM and start fresh.
So what actually happened there?
Hello, after installing twrp this one does not stay, do you have a solution? thank you
Thanks a lot for your work!
I hope Sagit can get recovery by ZCX
Sent from my Xiaomi Mi 6 using XDA Labs
TWRP 3.1.1-1 release:
Fixes the nandroid backup/restore issue
(Notice: backups made using old recovery builds still won't restore fine)
Other updates
Also for some of you've have been wondering,
MY RECOVERY KEEP GETTING REPLACED WITH STOCK RECOVERY... WHAT KIND OF MAGIC IS THIS?
The file: /system/bin/install-recovery.sh present in stock system is responsible for that.
You can simply stop this from happening by deleting it or renaming it to install-recovery.sh.bak using any root explorer or via TWRP (Advanced -> File Manager).
I am trying to install TWRP and root my Mi Mix. I have followed the steps below without encountering any error messages.
1. Go into fastboot
2. Flash TWRP recovery
3. Boot into recovery.
But at the end when I boot into recovery I see Mi Recovery 3.0 instead of TWRP. Am I missing anything? My device is unlocked. I am currently running MiUI 9.6.1 Global stable Android 8.0
sofene said:
I am trying to install TWRPA on my Mi Mix. I have followed the steps below without encountering any error messages.
1. Go into fastboot
2. Flash TWRP recovery
3. Boot into recovery.
But at the end when I boot into recovery I see Mi Recovery 3.0 instead of TWRP. Am I missing anything? My device is unlocked. I am currently running MiUI 9.6.1 Global stable Android 8.0
Click to expand...
Click to collapse
Never mind I solved the problem by booting from the pc. But I have a new problem. Two problems really. First of all I can't seem to get the data partition backed up. I get the error unable to mount *\data *. Secondly I cannot install magisk.zip. I cannot find the file in twrp though it is in main storage in the device. Do I need to copy it to any specific location for the twrp to use it?
Same like your firs post. But i not try instal magisk. I using SU. Now not root and not cusum recovery
sofene said:
Never mind I solved the problem by booting from the pc. But I have a new problem. Two problems really. First of all I can't seem to get the data partition backed up. I get the error unable to mount *\data *. Secondly I cannot install magisk.zip. I cannot find the file in twrp though it is in main storage in the device. Do I need to copy it to any specific location for the twrp to use it?
Click to expand...
Click to collapse
You can install it using a usb stick or via sideload.
You cant backup because the twrp's dont let you enter the password for the encryption on the device thus leaving it encrypted.
If u dont want to delete everything then use sideload for the Magisk installer, if u dont mind then u can go ahead and format data and the encryption will be gone untill you go back to system, then the device will encrypt the data again.
sexlord89 said:
You can install it using a usb stick or via sideload.
You cant backup because the twrp's dont let you enter the password for the encryption on the device thus leaving it encrypted.
If u dont want to delete everything then use sideload for the Magisk installer, if u dont mind then u can go ahead and format data and the encryption will be gone untill you go back to system, then the device will encrypt the data again.
Click to expand...
Click to collapse
I tried to install magisk using sideload enabled but still got error unable to mount storage at the end so I deleted data. And then I was able to install magisk without error. However, when I check root status with root checker it says root was not properly installed. When I went back to twrp I was presented with a screen to enter password to mount I guess the storage or partition. Does this mean that ruth has been installed even though root checker says its not.? Secondly which password is being requested because when I entered my screen unlock password it says password failed. Is it asking for the mi account password or with other password? Thanks for your assistance.
Hi, the only thing that worked for me is to install right after the rom the encryption disabler and you'll be able to use trwp. Just follow the steps in the link below. last thing, when you'll make an update you'll loose again the trwp access.
https://forum.xda-developers.com/mi-mix/development/rom-global-miui9-oreo-mi-mix-t3783869
lnt976 said:
Hi, the only thing that worked for me is to install right after the rom the encryption disabler and you'll be able to use trwp. Just follow the steps in the link below. last thing, when you'll make an update you'll loose again the trwp access.
https://forum.xda-developers.com/mi-mix/development/rom-global-miui9-oreo-mi-mix-t3783869
Click to expand...
Click to collapse
Thanks for your reply. One question, though. Would this then allow you to backup data using twrp?
sofene said:
Thanks for your reply. One question, though. Would this then allow you to backup data using twrp?
Click to expand...
Click to collapse
Yes you can make a backup, but in case of update you'll loose the access on your files in trwp.
A couple things :
1. You can't install magisk if your data partition is encrypted, because magisk needs to put the file in the data partition. so you need to disable the encrypt first, and then you can install magisk.
2. If your data partition is encrypted, don't bother to backup from twrp. Boot to system, connect to pc, and backup using regular way (copy and paste files).
3. Backup your data before you do any encrypt/decrypt process.
This version of TWRP works on both the TB-X605F (wifi) and TB-X605L (LTE). It does not work for the TB-X605FC/FL (Tab M10 FHD Rel).
Warning: this TWRP is for the Lenovo Smart Tab M10 with the Snapdragon 450 (SDA450) chipset. This image will not work for the second gen M10 (TB-X606F/L), which use a Mediatek SOC. See this thread.
For the M10 HD (TB-X505F/L), see this thread. For the TB-X505X, see this thread.
Code:
#include <std_disclaimer.h>
/*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Possible issues with TB-X605L
If the latest version of TWRP for TB-X605F doesn't work for your TB-X605L model, try version 3.4.0-0 from twrp.me.
Installation
TWRP for this device is officially supported. You can download it from twrp.me or in the TWRP App (from the PlayStore). Installation instructions are included on twrp.me.
It is recommended that you also install Magisk. This will ensure TWRP remains your default recovery.
Step-by-step guide
download TWRP to your PC (see the Download section below)
download magisk.zip to your MicroSD or OTG device. Get the latest Magisk zip file here.
if your bootloader is already unlocked, go to step 4. To unlock bootloader:
on tablet: go to Settings->System->About and press "Build number" 7 times to enable Developer Options.
on tablet: go to Settings->System->DeveloperOptions. Turn on: "OEM unlocking" and "USB debugging".
connect tablet to your computer. Tablet will ask for permission to "Allow USB debugging". Tick "always allow" and select "OK".
backup any files you want to keep to an external device (MicroSD/OTG/computer), because the next step will wipe all your photos, files, google account etc on the tablet.
Now unlock the bootloader:
Code:
adb reboot bootloader
fastboot oem unlock-go
fastboot reboot
flash the twrp image:
Code:
adb reboot bootloader
fastboot flash recovery twrp.img
if you haven't loaded Magisk yet, go to step 6. If you have already loaded Magisk, you can just reboot and you're finished:
Code:
fastboot reboot
adb reboot recovery
load Magisk (step one): reboot to recovery. Do not reboot into the system, because it will over-write TWRP with stock recovery. If that happens, go back to step 4 and start again. When you issue the reboot command (below), you have to immediately press the button combination to reboot to recovery (TWRP). Here are the steps:
issue the reboot command:
Code:
fastboot reboot
immediately press and hold all three buttons (Pwr+VolUp+VolDown). The tablet might reboot twice. Release all the buttons when you see the TWRP screen, or hear your PC acknowledge that ADB is connected.
load Magisk (step two): flash Magisk. In TWRP:
select "Install"
use "select storage" to locate device you stored magisk.zip on.
press the OK button
select the Magisk zip file
swipe to confirm Flash
when Magisk is finished, hit the back button to go back to main TWRP screen.
select "Reboot" then "System"
if the Magisk Manager app wasn't automatically loaded, you can get it here.
finished!
If you prefer to use button combos, rather than fastboot/ADB commands:
Vol Down + Power = fastboot mode
Vol Up + Vol Down + Power = recovery mode
Changelog
Code:
02/03/2022 - TWRP 3.6.1_9: new TWRP release
23/11/2021 - TWRP 3.6.0_9: new TWRP release
01/01/2021 - TWRP 3.5.0-0: new TWRP release
21/11/2020 - TWRP 3.4.0-1: new official version with SPL patch
19/11/2020 - promoted security patch level to 2099-12-31. No need to worry about SPLs ever again.
02/09/2020 - promote security patch level to 2020-08-01 for TB-X605F_S210208_200807_ROW
06/08/2020 - officially supported
31/07/2020 - upgrade to TWRP 3.4.0-0
- data decryption working (security patch 2020-04-01)
- landscape mode (by popular demand)
- add more partitions to Backup options
15/01/2020 - reverted to API 28 (Android Pie)
- renamed "sdcard1" to "external_sd"
- changed [ro.build.incremental.version] in preparation for OTA #4
24/11/2019 - fixed date/time & EDL reboot mode
- dropped back to API 27
20/11/2019 - initial commit (API 28) - encryption/decryption not working
Downloads
official​
TWRP for X605F: twrp.me
Source code
github.com/minimal-manifest-twrp/platform_manifest_twrp_omni/tree/twrp-9.0
github.com/TeamWin/android_device_lenovo_X605F (official)
github.com/Yahoo-Mike/recovery_device_lenovo_X605F (unofficial)
FAQ
See the third post for answers to some FAQs like:
Will this TWRP work with other M10 and P10 devices?
Why is my "Data" partition empty (0 MB)?
how do I root my device?
Credits
The guys at TeamWin Recovery Project.
Everyone whose device trees I plagiarised from GitHub.
The amazing work of @Chaser42, @Long_Sam and others to get this project started.
XDA:DevDB Information
X605F Recovery, Tool/Utility for the Lenovo Thinkpad Tablet
Contributors
Yahoo Mike, Chaser42
Source Code: https://github.com/TeamWin/android_device_lenovo_X605F
Version Information
Status: Testing
Created 2019-11-19
Last Updated 2022-05-22 (v3.6.1 and warning for TB-X605L)
Encryption/Decryption
When you load the stock ROM, it creates and automatically encrypts the data partition. If you are not using the correct TWRP version, the data partition might be empty (0 MB). This is because TWRP failed to decrypt the data partition.
If your data partition is 0MB in TWRP, make sure you have loaded the latest version of TWRP (Nov 2020 or newer). Older builds required the security patch levels to match on TWRP and your system.
If you want to remove encryption completely, then you can use the dm-verity-forceencrypt tool. @turboperson123 has put together some instructions to remove encryption. If you've already loaded TWRP, then you only need to follow steps 6 and 7 from that post. @turboperson123 's method uses @Zackptg5 's Universal DM-Verity, ForceEncrypt, Disk Quota Disablers tool to remove encryption and dm-verity.
FAQs
Can I use this TWRP on other M10 and P10 tablets?
There are quite a few variants of these Tabs that use the Snapdragon 450 (SDM450) chipset:
TB-X605F (Tab M10 wifi) - tested working this TWRP
TB-X605L (Tab M10 LTE) - tested working with TWRP ( thanks @alexupsa )
TB-X705F/L (Tab P10) - no. Use the twrp available on this thread.
For the TB-X505F/L (M10 HD) see this post.
NOTE: the TB-606F/L (M10 2nd gen), TB-X605FC (M10 FHD) use different chipsets, so this TWRP won't work.
Why is my "Data" partition 0MB?
See the second post in this thread.
What should I backup?
Short answer: everything.
But the bare minimum might include:
System Image
Vendor Image
Firmware/Modem
Persist
Data
Cache
Boot
How do I root my device?
To root your device, here are the instructions for the:
X705F (thanks to @Chaser42)
X605F/L - follow steps 6 & 7 in the OP above. If you don't want to load TWRP, then try something like @Long_Sam's patched boot.img method.
X505F/L - follow the "step by step guide" in the OP above. Just make sure you use twrp for X505F (not for X605F).
How do I load OTAs with TWRP?
Note: if you ran the dm-verity-forceencrypt tool to unencrypt your /data, then the steps below will not work.
select "uninstall" in the Magisk Manager app. If MM doesn't reboot the system, then reboot - this will re-install stock recovery.
install the OTA (either in the system or using stock recovery).
re-flash TWRP (for the new security patch level)
re-install Magisk
TB-X605L working properly. Thank you!
TB-X605L working properly. Thank you!
Yahoo Mike said:
This is a work in progress. Volunteer testers are very welcome.
Click to expand...
Click to collapse
Wow...
That's really huge...
As we say here : "Monsieur, chapeau bas !"
Long_Sam
Lenovo has released quite a few variants of the Tab M10 now. I'm not sure this TWRP will work on all of them.
There are now even variants of a variant !
Code:
[B]M10[/B] with SDM-450 models: X605F (wifi) & X605L (LTE)
[B]M10 HD[/B] with SDM-429 models: X505F (wifi), X505L (LTE) & X505X (LTE Bands 1,2,3,4,5,7,8,20,38,40)
[B]M10 FHD[/B] with SDM-450 models: X605FC (wifi) & X605LC (LTE)
The M10 I have is shipped with a Snapdragon 450 (SDM-450) chipset & Hardware Code 63. But I see on their US site that Lenovo are now putting the SDM-429 in the X605. This might cause a problem with TWRP. I'm not sure if the kernels will be compatible.
The TWRP I've posted is for the X605F/L SDM450 (HW=63). I might need to compile a different TWRP for the SDM429 versions of the X605 & the X505.
If your X605 or X505 shipped with the SDM429, can you let me know if this TWRP works ? I need to know the Hardware Version, CPU and Hardware Code. Hardware Version and CPU are in System->About. The Hardware Code is in brackets after the S/N on the sticker on the back of the tablet, eg S/N Hxxxxxxx (63).
If you have an X605FC/LC, let me know if this TWRP works. I think it will, but I want make sure.
I have one with the 429 TB-X505F SD429 HW71 If i get some time today I might be bale to try it. I'll post soon as I do.
This morning I successfully compiled and ran the P10 kernel source on my M10. I had to tweak the config a bit. I tested it in TWRP. No problems.
Tomorrow, I'll inject it into the boot.img of the system ROM and see what happens. If it is mostly stable, then we're on the way to LOS for the M10. If it's completely stable, I'll push the source up to github.
I'll continue to use the stock kernel for the released versions of TWRP in this thread, though.
Thanks to @clsA for helping me work out that the M10 kernel is a subset of the P10 kernel.
@Yahoo Mike
thx for the twrp
succesfully flashed on my X605L
"Stock recovery image (recovery_stockROM.img) from TB-X605F_USR_S200065_1905280020_Q00332_ROW - just in case something goes wrong & you need to restore stock recovery. Only use this image on a TB-X605F. If you need it for any other variant, just ask in this thread and we'll track it down for you."
do you have the stock recovery for the X605L ?
how can i backup "DATA" inside twrp ?
will this help ?
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
OSIRIS2010 said:
...
do you have the stock recovery for the X605L ?
Click to expand...
Click to collapse
Now I think of it, you don't need it. If TWRP fails to flash, then stock recovery will still be there. If stock recovery is still not loading, just boot into the system and shutdown. When you shutdown, the system will re-flash stock recovery for you.
OSIRIS2010 said:
...
how can i backup "DATA" inside twrp ?
Click to expand...
Click to collapse
Have a look at the second post.
TL;DR...the dm-verity-forceencrypt tool will do it. But it will break the next OTA. The unencrypted P10 guys are having problems at the moment with this.
I've tried to get TWRP to unencrypt the data partition, but I can't get KeyMaster to initialise successfully. Maybe the next version of TWRP will be able to do it.
Yooo. Sorry I took so long works been crazy. I cant get it to reboot into twrp recovery. Its flashes the 605 recovery then I follow the next steps in the guide but I can only get it to reboot to the stock recovery screen. Run the reboot recovery command then immediately hold the volume + - down along with power. I tried a lot I let reboot twice then let off, and nothing then I tried several more times. Reflashing then the next step. I must not be holding my mouth...err I mean pushing the buttons right or the recovery just isn't gonna work. Add I'm very newbie at rooting and customizing. I've I've rooted one phone. A 70$ moto g5 plus I got off Ebay that was basically brand new. Installed twrp recovery and magisk. I bought that cause I have SD note 9 I cant root and have this need to play YouTube videos in my truck lol. Let me know if you have any suggestions I can try. Or ideas that might make it work. I pretty much fubard the tab and (at a different time) before I tried this recovery and was able to reflash stock img though odin.
11mackey11 said:
Yooo. Sorry I took so long works been crazy. I cant get it to reboot into twrp recovery. Its flashes the 605 recovery then I follow the next steps in the guide but I can only get it to reboot to the stock recovery screen. Run the reboot recovery command then immediately hold the volume + - down along with power. I tried a lot I let reboot twice then let off, and nothing then I tried several more times. Reflashing then the next step. I must not be holding my mouth...err I mean pushing the buttons right or the recovery just isn't gonna work. Add I'm very newbie at rooting and customizing. ...
Click to expand...
Click to collapse
Don't be too hard on yourself...you've done well to get this far.
I just had a quick look at the kernel for the X505F. It's very different from the X605F. So this TWRP definitely won't work for you. Sorry.
If you want me to build a TWRP for the X505F, PM me and we'll work something out.
How do you remove twrp I think that or magisk is giving me the booting issues. Half the time I reboot for things it gets stuck. Not sure if it's root or twrp but I can't seem to remove either.
cbomb1337 said:
How do you remove twrp I think that or magisk is giving me the booting issues. Half the time I reboot for things it gets stuck. Not sure if it's root or twrp but I can't seem to remove either.
Click to expand...
Click to collapse
If you uninstall Magisk, then the system will overwrite TWRP with stock recovery the next time you reboot. Just tap "uninstall" in the Magisk Manager app. You can also remove Magisk from TWRP following these instructions.
What kind of boot issues are you having? Are you using a TB-X605F with SDA450? Or is it something similar?
I am using Tb 605f it seems to be booting fine now after removing this riru module and edxposed. I'll just leave that and stick with just viper 4 Android lol
Do you know if them modules for increasing speed work? I think one of them was called fde and there the doze one.
cbomb1337 said:
I am using Tb 605f it seems to be booting fine now after removing this riru module and edxposed. I'll just leave that and stick with just viper 4 Android lol
Do you know if them modules for increasing speed work? I think one of them was called fde and there the doze one.
Click to expand...
Click to collapse
Good to hear it's all working again.
Sorry, I haven't tried any of those tweaks.
Lenovo have updated the stock ROM they serve for the TB-X605F through LMSA rescue. It's now at TB-X605F_USR_S210126_1910290024_Q00332_ROW. This is the latest update. There are no OTAs to apply. The M10 is due for a security OTA pretty soon, though. The P10 has already received it.
Unfortunately, it's no longer possible to post a direct link to Lenovo's website for this ROM. You'll have to use LMSA to get it.
FYI. Lenovo have changed how they serve the stock ROM. The ROM is now kept at rsdsecure-cloud.motorola.com. LMSA seems to generate (or request and receive) a one-off time-limited credentialed ticket for the download. You can't download the zip files without the credentials attached to the URL.
If you really want to, you can still intercept the URL in download_resources.json in the LMSA download folder.
is there anything new in the update. i might hold of because i dont want to lose root.
cbomb1337 said:
is there anything new in the update. i might hold of because i dont want to lose root.
Click to expand...
Click to collapse
No, there's nothing new. This isn't really an update, it just seems to be a consolidation of the old stock ROM and incremental OTAs.
This is only for M10 wifi (TB-X605F) with SDA450.
The latest OTA for TB-X605F has just landed. It's available on your tablet, or directly from: TB-X605F_USR_S210126_191029_Q00332_ROW_TO_TB-X605F_USR_S210152_200120_Q00332_ROW_WCE26E2CD5.zip.
The update takes the M10 to:
Code:
build: TB-X605F_USR_S210152_200120_ROW
security patch: 1 January 2020
kernel: 3.18.120-perf-gd60e12b6-dirty
If you have TWRP and root, you'll need to:
select "uninstall" in the Magisk Manager app
install the OTA (from SD card) in recovery and reboot
re-flash TWRP
re-install Magisk
only if you unencrypted the data partition
If you have unencrypted your data partition, it will be re-encrypted during this process. Make sure you back it up before you start the OTA. You might also need to restore the TWRP backup you made of the vendor partition, before the OTA will run. Once the OTA, TWRP and Magisk are installed, you can re-run the dm-verity tool.
Hi!
My only encounter with rooting was several years back when it used to be a simple affair (one click rooting app based on exploits like framaroot etc), so please bear with me.
I'm on Stock Oreo 8.1 (Patch 1 Aug 2019) Sanders 1804 (India) version. I've followed various guides and have been successful in flashing TWRP 3.4.0 (Official Sanders version) and Magisk 20.4. But everytime the phone is rebooted, TWRP can't mount internal storage and shows 0mb.
I tried all three methods I could find:
1. dm-verity zip flashing - Log said fstab not found. Searched and found that from Oreo, Android's encryption approach has been changed. I couldn't make much sense out of those, though.
2. Manually replacing the `forceencrypt` to `encryptable` then flash stock recovery and format data. Didn't work.
3. Formatting data right after TWRP is flashed. Didn't work either.
The maximum it works is for one time when I can connect the device to laptop to add some zips to it to flash. It doesn't make sense to wipe the data when it's the data only that we want to back!
My purpose is to make flashable zip (nandroid) to revert to if anything goes wrong. It was phone's wifi frequent disconnection (or connected but no internet) issue which forced me to try root. I'm not much interested in new ROMs and am fine with stock itself but need a backup of all apps with data etc. Also, I couldn't understand clearly the FAQ on TWRP website that says TWRP doesn't backup internal storage but backup data. As I don't use SdCard, the internal storage is mounted in /sdcard folder only
I'll really appreciate if someone can help me.
Thanks
Found solution from a helpful guy in a Telegram group.
1. Use ONLY attached zip/img files and follow exact same order.
2. Flash TWRP, reboot to recovery
3. In Wipe section, choose Format data, type YES and confirm. Reboot to recovery again.
4. Flash DM-Verity-ForceEncrypt.zip file. Flash Magisk.zip file. Reboot to recovery.
5. (Optional) Make a backup if you want or Reboot to system. Done!
https://drive.google.com/drive/folders/1h8wb78wLH5_VBmkhjpDjyPyDbUG9ZBV4?usp=sharing