DisclaimerThis software comes with no warranty,XDA staff ,myself or TeamWin stuff can't be hold responsible for any damage it may cause to your device.
Note: Currently Oreo 8.1 custom roms are not supported,only stock EMUI 8.x .
Download and Installation
* Download twrp recovery
* Start your device in fastboot mode
* Install the recovery using the following command:
Code:
fastboot flash recovery_ramdisk [name of the file].img --> ex: fastboot flash recovery_ramdisk twrp_clt_0.1.img
* Restart with this command:
Code:
fastboot reboot
* As soon as you execute the restart command,remove the USB cable and keep pressing Volume UP,so the device will boot to TWRP.This is to avoid that the device boot to OS,overwritting TWRP recovery.
Features
Internal storage decryption = working (if it pin/password, pattern fails then try by removing them (password, pin, pattern, fingerprint) from Android before booting to TWRP.
MTP and OTG connection = working
Backup&Restore = working
Note: This was tested only by few P20 Pro owners,so if you test it,please report back!There are no sources for this yet,because is based on the work of @zxz0O0 ,from Honor 9 forum.
Credits
**** @zxz0O0 - This wouldn't be possible without this guy,so big big thank to him.I used his base to make this recovery work ,so in sign of respect his nick will also be on the TWRP boot screen.Thank again buddy!
**** TeamWin project ,obviously.
Download links
twrp_clt_0.1.img - Decryption support (you can use the same password/pin/pattern to decrypt in TWRP), /recovery_ramdisk not available for backup./vendor not available for backup (use /vendor_image instead)
Glad to see this. Any chance of sources or a pull request on my device tree to get decryption working?
hum.. it seem that decryption working great.
See :
Internal storage decryption = working
MTP and OTG connection = working
Backup&Restore = working
Yes. I was just asking for sources or a pull request on my Github repository. IMHO the decryption method used would be useful for anybody interested in ROM/Recovery development - and also required to comply with XDA licensing / GPL requirements.
a1Pha said:
Yes. I was just asking for sources or a pull request on my Github repository. IMHO the decryption method used would be useful for anybody interested in ROM/Recovery development - and also required to comply with XDA licensing / GPL requirements.
Click to expand...
Click to collapse
This is not based 100% from sources, i have another version with working decryption, which is based on open source tree, bur it's not ready yet, just private testing.
This is not breaking any GPL/XDA rule, because it's using just a dummy kernel, not compiled or modified by me! ?
Pretoriano80 said:
This is not based 100% from sources, i have another version with working decryption, which is based on open source tree, bur it's not ready yet, just private testing.
This is not breaking any GPL/XDA rule, because it's using just a dummy kernel, not compiled or modified by me! ?
Click to expand...
Click to collapse
Thanks for clarification. Would you mind sharing some details via PM with me? I'd be glad to improve my repo
a1Pha said:
Thanks for clarification. Would you mind sharing some details via PM with me? I'd be glad to improve my repo
Click to expand...
Click to collapse
Yes, no problem! Also have a look at my Github (pretoriano80). My goal is also to make a fully open source version. ?
Quote: Note: This was tested only by few P20 Pro owners,so if you test it,please report back!
Hi Pretoriano80, Hi All,
Great job ! Just installed... I confirm that it works on my CLT-L29 8.1.0.106(C432)
Internal storage decryption, MTP and usb OTG connection, Backup& Restore (incl /vendor_image) : All working !
Many thanks & Cheers
CLT-L09 (C782) all is working as it should, successful backup and mount of my 1tb hard drive.
Absolutely fantastic work
Thanks :good:
Well this is very positive.
Less than 2 calendar weeks from release to TWRP release.
I think we can possibly have pretty high expectations for development on the P20 Pro.
Hey im getting this when I attempt to run the fastboot flash recovery command:
C:\Users\andre\Desktop\twrp>fastboot flash recovery_ramdisk twrp_clt_0.1.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (23542 KB)...
OKAY [ 0.151s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.171s
Can anyone advise please?
andrewglass3 said:
Hey im getting this when I attempt to run the fastboot flash recovery command:
C:\Users\andre\Desktop\twrp>fastboot flash recovery_ramdisk twrp_clt_0.1.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (23542 KB)...
OKAY [ 0.151s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.171s
Can anyone advise please?
Click to expand...
Click to collapse
You have to unlock bootloader first!
Pretoriano80 said:
You have to unlock bootloader first!
Click to expand...
Click to collapse
Yep - I forgot that step - had the code but missed it out lol - Im an idiot lol
whats difference between your version and a1pha?
also does this trigger safety net? (i installed magisk via patched ramdisk.img and google pay wont work) will it work with TWRP (no root)
virtyx said:
whats difference between your version and a1pha?
also does this trigger safety net? (i installed magisk via patched ramdisk.img and google pay wont work) will it work with TWRP (no root)
Click to expand...
Click to collapse
Have you made sure that the Google Pay app is selected in the Magisk Hide list in the app? It doesn't tick automatically like it used to with Android Pay. You should pass safetynet with Magisk installed. Also, after flashing TWRP still passes safetynet too.
virtyx said:
whats difference between your version and a1pha?
also does this trigger safety net? (i installed magisk via patched ramdisk.img and google pay wont work) will it work with TWRP (no root)
Click to expand...
Click to collapse
TWRP has nothing to do with SafetyNet! Maybe you installed a firmware which didn't passed Google check yet.
Is this what I actually need to do to root my P20 Pro?
I unlock the bootloader, flash the twrp recovery, then install supersu.zip via twrp recovery and I'm done, right?
Or is there something else I left out?
Thank you very much so far!
m00h said:
Is this what I actually need to do to root my P20 Pro?
I unlock the bootloader, flash the twrp recovery, then install supersu.zip via twrp recovery and I'm done, right?
Or is there something else I left out?
Thank you very much so far!
Click to expand...
Click to collapse
Try Magisk instead of SuperSU. It has better support for Oreo than the latter.
BTW anyone here tried flashing Magisk to root the device?
DJBhardwaj said:
Try Magisk instead of SuperSU. It has better support for Oreo than the latter.
BTW anyone here tried flashing Magisk to root the device?
Click to expand...
Click to collapse
I did on the other TWRP thread, worked fine.
The page for getting an unlock code seems to 404 for me. Is this happening for anyone else too?
Related
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom "ROM" like OmniROM
Click to expand...
Click to collapse
WARNING!!! Be careful what you do here. One mistake and the device is soft-bricked. I take no responsibility for bricked devices, lost warranty or even OTAs not working!! Booting and/or flashing files from this post is on your own risk.
Requirements
Unlocked bootloader
Yoga Tablet 3 Plus with and without LTE (YT-X703L and YT-X703F) are supported
Known Issues
WARNING! Our device uses dm-verity (verified boot). The system partition should remain read-only. Otherwise a bootloop will occur. You can flash my modified kernel or SuperSU to resolve this but OTA's are no longer possible! You have to restore a factory image or clean system backup to receive OTAs
Potentially DRM keys are lost! Pure unlocking and rooting does not cause the issue. However, there have been reports of lost DRM keys by some unknown action. It is advised to act with caution. Losing your DRM keys can lead to issues with some apps which use DRM which could then have limited or no functionality. E.g. Netflix will only stream in SD (480p). You can check with DRM info if you still have L1 security level which means DRM keys are intact.
Download
Official TWRP for YT-X703F (Wifi): twrp.me
Official TWRP for YT-X703L (LTE): twrp.me
Instructions
Install fastboot and adb on your PC, e.g. from here
Enable developer options and in there select to unlock your bootloader by enabling OEM unlock and enable USB debugging
Connect your PC to your tablet and run
Code:
adb reboot bootloader
using adb on command line. The tablet will reboot into bootloader mode where you will only see the Lenovo logo. Now you use
Code:
fastboot oem unlock-go
to unlock. This will factory reset your device
Setup the tablet again and reboot again to the bootloader
Then run
Code:
fastboot boot twrp-3.2.1-0-yt_x703f.img
to temporarily boot into TWRP. You can also flash if you are sure
Select to keep system read only when TWRP starts to avoid modification which will make OTAs impossible
Optionally flash SuperSU or Magisk in TWRP which should install system less. Keep OEM unlock enabled if you flash or modify anything
Additional Downloads
Backup of original boot, recovery and system image for YT-X703F S000936: MEGA
Modified Boot image with forceencrypt disabled and it switches off CABC fully. You need to factory reset after flashing to format data without encryption boot_yt_x703f_s000963_noforceencrypt_cabc.img (YT-X703F S000963) / boot_yt_x703l_s000963_noforceencrypt_cabc.img (YT-X703L S000963) . Use
Code:
fastboot flash boot boot_yt_x703f_s000963_noforceencrypt_cabc.img
to flash the kernel in fastboot. SuperSU or Magisk should be flashed afterwards if root is desired.
Full factory images with flash tool and instructions YT_X703F_S000689, YT_X703L_S000704, YT_X703F_S000725, YT_X703L_S000725, YT_X703F_S000734, YT_X703L_S000734, YT_X703L_S000744, YT-X703F_S000744, YT-X703L_S000963, YT-X703F_S000963 and OTA updates: MEGA (These images contain the individual boot, recovery and system images that you need to restore from any modification mentioned above)
System Updates (OTA)
In order to successfully apply Lenovo system updates after root you have to restore the original boot, recovery (if you flashed TWRP) and system partitions from your current installed version (e.g. S000744) for your variant of the tablet. This will NOT delete your apps and data but will unroot. Note that OTAs are block based and always check the contents of most of the partitions. This means that all of these partitions (except your data) have to be original and have to be on the exact same version (e.g. S000734) for the update to succeed.
See here for instructions how to restore the partitions with fastboot.
Credits
@pogo1975 - for providing the factory images and fixing the AV sync issue
@launcher20 and @deecept - for testing the LTE version
TeamWin
Changelog
v4:
Now official TWRP with version 3.0.3-0
v3:
enable full disk encryption for access to the encrypted data partition
update TWRP kernel to latest S000725 version
v2:
add support for LTE variant (YT-X703L)
add further mount points to be able to backup more data
Thanks buddy! You are an absolute champion! Tell me what you need me to do and I'll do it before rooting and up load what you need.
Doing good work here.
Who wants to bet on a race between matshias and Lenovo support for who can fix the issues with this device first?
That's great and fast, I'm thinking tab 3 plus is getting hot now.
Great to see there is something moving for the yoga now. You think it will support the lte Version anytime? Or maybee even lineageos?
so you know, i've managed to install xposed thanks to this thread https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268 and is working well.
wayney said:
Thanks buddy! You are an absolute champion! Tell me what you need me to do and I'll do it before rooting and up load what you need.
Click to expand...
Click to collapse
Well if you haven't modified anything yet then it'd be great if you can boot into TWRP with system read only and then connect via ADB to the tablet with a big SD card inserted which has enough free space (4 GB).
The run the following command
Code:
dd if=/dev/block/bootdevice/by-name/system of=/sdcard1/system.img
This will take a while. Then copy the file system.img from your SD card to a PC and zip it (or 7z, rar). Then upload it
Gogoho said:
Great to see there is something moving for the yoga now. You think it will support the lte Version anytime? Or maybee even lineageos?
Click to expand...
Click to collapse
The LTE variant is probably very similar and it wouldn't be much work. But I don't own the device, so I would need some help. So someone with the LTE variant who is not afraid to experiment with fastboot and adb and who can provide me with the details needed I am happy to compile a TWRP for it.
LineageOS is much much more work than TWRP. For an experienced cyanogenmod/LineageOS dev it is not much of a thing and would take only a few days, especially since it is a Qualcomm device and there are already ports for devices with SD 652. But for me this is new as well so it'll take much longer. As soon as I have time I'll look into it.
matshias said:
Well if you haven't modified anything yet then it'd be great if you can boot into TWRP with system read only and then connect via ADB to the tablet with a big SD card inserted which has enough free space (4 GB).
The run the following command
Code:
dd if=/dev/block/bootdevice/by-name/system of=/sdcard1/system.img
This will take a while. Then copy the file system.img from your SD card to a PC and zip it (or 7z, rar). Then upload it
Click to expand...
Click to collapse
You forgot to tell me to go to adb shell :silly:
DD is currently doing a dump, non interactive so I hope it is still alive, it has been close to 1 hour so far. I will upload the clean image once it is done and await further instructions from you. :good:
I'm in Perth, Western Australia (UTC +8:00), so we might be playing timezone tag.
wayney said:
You forgot to tell me to go to adb shell :silly:
DD is currently doing a dump, non interactive so I hope it is still alive, it has been close to 1 hour so far. I will upload the clean image once it is done and await further instructions from you. :good:
I'm in Perth, Western Australia (UTC +8:00), so we might be playing timezone tag.
Click to expand...
Click to collapse
I think I forgot one more thing. The external SD card needs to be mounted in the TWRP menu. I believe it's not mounted automatically. So the DD command does nothing. It shouldn't take that long. Sorry about that!
It's UTC +1:00 here in Germany
matshias said:
Well if you haven't modified anything yet then it'd be great if you can boot into TWRP with system read only and then connect via ADB to the tablet with a big SD card inserted which has enough free space (4 GB).
The run the following command
Code:
dd if=/dev/block/bootdevice/by-name/system of=/sdcard1/system.img
This will take a while. Then copy the file system.img from your SD card to a PC and zip it (or 7z, rar). Then upload it
Click to expand...
Click to collapse
matshias said:
I think I forgot one more thing. The external SD card needs to be mounted in the TWRP menu. I believe it's not mounted automatically. So the DD command does nothing. It shouldn't take that long. Sorry about that!
It's UTC +1:00 here in Germany
Click to expand...
Click to collapse
I was wondering why nothing was happening after 3 hours.
I have rared it and it is uploading at the moment, it is going to take 5 hours.
wayney said:
I was wondering why nothing was happening after 3 hours.
I have rared it and it is uploading at the moment, it is going to take 5 hours.
Click to expand...
Click to collapse
Wow ok. Well thanks a lot for your efforts. This will not just help me but anyone with modified system partition to get OTAs.
Unmodified System Image
Here is the vanilla image via DD of the system partition.
Software Version : YT-X703F_160817
Android Version : 6.0.1
Security Patch Level : 1 September 2016
Kernel Version : 3.10.84-perf
Build Number : YT-X703F_S000689_161105_ROW
Tablet purchased retail from Australia.
https://mega.nz/#!bos0GIjI!vcO9dpSJX...Grjb7k3z6mjnqA
wayney said:
Here is the vanilla image via DD of the system partition.
Software Version : YT-X703F_160817
Android Version : 6.0.1
Security Patch Level : 1 September 2016
Kernel Version : 3.10.84-perf
Build Number : YT-X703F_S000689_161105_ROW
Tablet purchased retail from Australia.
https://mega.nz/#!bos0GIjI
Click to expand...
Click to collapse
Perfect!!
Can you send me the key for the download via PM or post it?
matshias said:
Perfect!!
Can you send me the key for the download via PM or post it?
Click to expand...
Click to collapse
Let's try that again.
https://mega.nz/#!bos0GIjI!vcO9dpSJXp6cKtdH07Kt0RSaqpqQ7Grjb7k3z6mjnqA
matshias said:
Wow ok. Well thanks a lot for your efforts. This will not just help me but anyone with modified system partition to get OTAs.
Click to expand...
Click to collapse
Thank you guys for spending times on it, it would be wonderful if Lenovo people do thing like this way, too.
In the depths of the Russian Internet i have found this
YT-X703F_USR_S000689_1611051146_Q00237_ROW.zip
https://drive.google.com/drive/folders/0B_jGuhC9WsNfYUZzZmhRY2NhQlU?usp=sharing
it is supose to be complete image to Wifi-Version.
I HAVE NOT FLASHED THIS YET. Do it on your risk.
pogo1975 said:
In the depths of the Russian Internet i have found this
YT-X703F_USR_S000689_1611051146_Q00237_ROW.zip
https://drive.google.com/drive/folders/0B_jGuhC9WsNfYUZzZmhRY2NhQlU?usp=sharing
it is supose to be complete image to Wifi-Version.
I HAVE NOT FLASHED THIS YET. Do it on your risk.
Click to expand...
Click to collapse
Hahaha got to love the dark corner of the Russian internets :laugh:
pogo1975 said:
In the depths of the Russian Internet i have found this
YT-X703F_USR_S000689_1611051146_Q00237_ROW.zip
https://drive.google.com/drive/folders/0B_jGuhC9WsNfYUZzZmhRY2NhQlU?usp=sharing
it is supose to be complete image to Wifi-Version.
I HAVE NOT FLASHED THIS YET. Do it on your risk.
Click to expand...
Click to collapse
If that's real it would have saved me a lot of time finding the loophole in the system to extract the boot and recovery image. But still a great find which will rescue some soft-bricked devices.
matshias said:
If that's real it would have saved me a lot of time finding the loophole in the system to extract the boot and recovery image. But still a great find which will rescue some soft-bricked devices.
Click to expand...
Click to collapse
so long as it's safe and not loaded with malware...
What?
A TWRP bootable-image and installer ZIP for stock-based ROM's (i.e. not LOS 15.1) and maybe others (untested).
Based on:
Latest TWRP build provided by @pl_blaze
The official TWRP installation script for Pixel 2 by Dees_Troy (will install to both slots automatically - more resilient than the other TWRP script)
The IMG uses official kernel 8.1.10 so might be flashable (not tested!)
Not compatible with LineageOS 15.1 because it uses some custom update API that isn't in this TWRP. I considered using the LOS 15.1 TWRP build in this, but it's not compatible with stock encryption (it always thinks the passcode is wrong).
Full credits to @pl_blaze and Dees_Troy for this. I just packaged up something new and wrote clear instructions.
Why?
The old TWRP thread is not maintained and people keep asking/reporting the same questions/problems. I will try to keep this up to date as long as necessary. This is also a more robust installation script, using magiskboot binary to unpack/repack the boot image.
How?
Uninstall Magisk first if you have it installed, just to be safe. Or reflash stock boot.img. (Might not be necessary - a dirty flash worked OK for me but YMMV).
Fastboot boot (hotboot) any existing working TWRP image. Don't worry about working encryption/data, we only need kernel access. For example...
Code:
fastboot boot oreo_3.2.2_recovery.img
... which can be downloaded from Google Drive here (thanks to whoever shared this, I think it's a pl_blaze reshare).
Download attachment ZIP installer and flash in hot-booted TWRP (it will flash to both slots)
Reboot to Recovery and (re-)flash Magisk, if you use it.
Profit
@pl_blaze brother always thank you for the contributions that you do without coming to the light .and thanks for you @op to post working twrp for stock
this twrp will work on 7.1.2 ? i'm now on aex rom
Thanks @CosmicDan for starting this thread. I started to implement @pl_blaze changes into the official TWRP but I've been failing miserably (I'm a noob). Can you provide sources for the images?
I can't trust binaries floating all over the internet if it's not from a reliable dev. If you've compiled it yourself I'll give a try.
I reshare this twrp img on Telegram group,I tested it, works without problem
Flash of permaent twrp not tested by me
It's a good twrp!
CosmicDan said:
What?
A TWRP bootable-image and installer ZIP for stock-based ROM's (i.e. not LOS 15.1) and maybe others (untested).
Based on:
Latest TWRP build provided by @pl_blaze
The official TWRP installation script for Pixel 2 by Dees_Troy (will install to both slots automatically - more resilient than the other TWRP script)
The IMG uses official kernel 8.1.10 so might be flashable (not tested!)
Not compatible with LineageOS 15.1 because it uses some custom update API that isn't in this TWRP. I considered using the LOS 15.1 TWRP build in this, but it's not compatible with stock encryption (it always thinks the passcode is wrong).
Full credits to @pl_blaze and Dees_Troy for this. I just packaged up something new and wrote clear instructions.
Why?
The old TWRP thread is not maintained and people keep asking/reporting the same questions/problems. I will try to keep this up to date as long as necessary. This is also a more robust installation script, using magiskboot binary to unpack/repack the boot image.
How?
Uninstall Magisk first if you have it installed, just to be safe. Or reflash stock boot.img. (Might not be necessary - a dirty flash worked OK for me but YMMV).
Fastboot boot (hotboot) any existing working TWRP image. Don't worry about working encryption/data, we only need kernel access. For example...
Code:
fastboot boot oreo_3.2.2_recovery.img
... which can be downloaded from Google Drive here (thanks to whoever shared this, I think it's a pl_blaze reshare).
Download attachment ZIP installer and flash in hot-booted TWRP (it will flash to both slots)
Reboot to Recovery and (re-)flash Magisk, if you use it.
Profit
Click to expand...
Click to collapse
what does mean "hot boot", sorry am novice, Not even he could boot boot recovery from Minimal ADB and fastboot ,,, What am I doing wrong?
View attachment 4438212
teacapan said:
Fastboot boot (hotboot) anwhat does mean "hot boot", sorry am novice, Not even he could boot boot recovery from Minimal ADB and fastboot ,,, What am I doing wrong?
Click to expand...
Click to collapse
Hot boot means you are not flashing the recovery image just running it temporarily. Stock boot image is untouched in this process.
Run
fastboot devices
To check whether your device is connected.
alkesh95 said:
Hot boot means you are not flashing the recovery image just running it temporarily. Stock boot image is untouched in this process.
Run
fastboot devices
To check whether your device is connected.
Click to expand...
Click to collapse
thanks for reply, if you look at the screenshot it looks I am connected, the point is that it does not load the file, it does not find it, so if it does not start in recovery I can not do anything I'm stuck.
teacapan said:
thanks for reply, if you look at the screenshot it looks I am connected, the point is that it does not load the file, it does not find it, so if it does not start in recovery I can not do anything I'm stuck.
Click to expand...
Click to collapse
Did you put your recovery into the fastboot forder?
Did you unpack the zip ?
Also check if the name of recovery image is the same
It's possible to make password for twrp
DELETED.
lef7er1s said:
Did you put your recovery into the fastboot forder?
Did you unpack the zip ?
Also check if the name of recovery image is the same
Click to expand...
Click to collapse
1-yes
2-yes
3-yes
Anyway thanks for try help me.
Yeah well, I'm still stuck where, some help would be very appreciated.
View attachment 4438552
View attachment 4438553
Polluktus said:
this twrp will work on 7.1.2 ? i'm now on aex rom
Click to expand...
Click to collapse
Not sure, I've only tested on stock Oreo. Try and and let us know!
atttoush said:
Thanks @CosmicDan for starting this thread. I started to implement @pl_blaze changes into the official TWRP but I've been failing miserably (I'm a noob). Can you provide sources for the images?
I can't trust binaries floating all over the internet if it's not from a reliable dev. If you've compiled it yourself I'll give a try.
Click to expand...
Click to collapse
Indeed, no I have not compiled it myself - just ripped from pl_blaze.
I have a Oreo source repo cloned now for other reasons, but I might try and compile TWRP myself. Although it's been a couple years since I've tried to compile device-specific stuff from an AOSP tree so I don't know how long that will take.
teacapan said:
thanks for reply, if you look at the screenshot it looks I am connected, the point is that it does not load the file, it does not find it, so if it does not start in recovery I can not do anything I'm stuck.
Click to expand...
Click to collapse
Sounds like you just need to learn more about how to use console tools. You need to make sure the "fastboot boot filename.img" command will have a "filename.img" that matches the img filename in the current directory. This is just an example - substitute "filename.img" for the real filename. Use the CD command to change directory to where the img is.
teacapan said:
Yeah well, I'm still stuck where, some help would be very appreciated.
View attachment 4438552
View attachment 4438553
Click to expand...
Click to collapse
Try renaming the img file to something simpler like oreo_twrp.img
Edit: ah yes, the file you are pointing to has to be in the same directory where you opened cmd window, as cosmicdan stated above
CosmicDan said:
Indeed, no I have not compiled it myself - just ripped from pl_blaze.
I have a Oreo source repo cloned now for other reasons, but I might try and compile TWRP myself. Although it's been a couple years since I've tried to compile device-specific stuff from an AOSP tree so I don't know how long that will take.
Click to expand...
Click to collapse
Glad you open this thread. I'll wait for your compiled version to give it a try
teacapan said:
Yeah well, I'm still stuck where, some help would be very appreciated.
Click to expand...
Click to collapse
I don't know man, these adb and fastboot binaries look old (2014?). Try to get recent ones. And repeat the process.
silv3rfox said:
Glad you open this thread. I'll wait for your compiled version to give it a try
I don't know man, these adb and fastboot binaries look old (2014?). Try to get recent ones. And repeat the process.
Click to expand...
Click to collapse
Thanks, i will.
teacapan said:
Yeah well, I'm still stuck where, some help would be very appreciated.
Click to expand...
Click to collapse
Before flashing recovery
CD C:\Users\YOUR_USERNAME\Desktop\Adb
teacapan said:
Yeah well, I'm still stuck where, some help would be very appreciated.
Click to expand...
Click to collapse
The name of the file is ending with .img, delete ending " .img ", see below that patched_boot without .img in the end
Thanks for this. I checked out the differences between this and the flashable zip I was using (twrp-3.2.1-1-installer-tissot-FIXED_By_DroiDMester) and found this:
Code:
# write the new boot image to boot block
write_boot() {
print "Writing new boot image to memory..."
cd "$tmp"
if $use_dd; then
dd if=boot-new-a.img of="$boot_block"_a
[ $? = 0 ] || abort "Failed to write boot image A! You may need to restore your boot partition"
dd if=boot-new-b.img of="$boot_block"_b
[ $? = 0 ] || abort "Failed to write boot image B! You may need to restore your boot partition"
else
flash_image "$boot_block" boot-new.img
fi
[ $? = 0 ] || abort "Failed to write boot image! You may need to restore your boot partition"
}
This also flashes it into boot_a and boot_b correct?
What other differences does this have over that?
Update for new year.
1-1-2020 Uploaded a version of twrp for Bold-N1 with working touchscreen.
thanks to the help of @vineethrp in This Post
Original thread hidden, since twrp build is fixed.
This initial version of TWRP, still has major issue. A second issue with the recovery is the screen will not turn on for about 30 seconds after boot. A time that lines up with the screen sleep timer. The touchscreen is not working. This has been a kernel issue on other devices that I am aware of.
The kernel source for th BOLD-N1 is released, and I have been reading through it. To no avail. I can't find the section that is checking for recovery mode.
For the time being, I have confirmed this version is working with the adb command line operations.
Partial list of functions found Here https://twrp.me/faq/openrecoveryscript.html
I have used the "install" and "sideload" operations.
In most cases (mods etc) sideload should be ok to try.
For the mod I was interested in (DM-Verity-No-Forceencrypt). The install does not support being done in sideload.
Because in the install script used, it checks the zip file name. Based on the file name it enables/disables options of the script.
Sideload changes the *.zip name, so more steps were necessary.
In the following steps, the device /data partition will be formatted. This will erase all your stored data, and more importantly,
it will remove the encryption.
The following steps require you to have already unlocked bootloader.
And,
As a reminder, whenever you modify your phone, you should NEVER relock the bootloader
INSTALL the attached TWRP img. Use Fastboot to install it.
Code:
fastboot flash recovery **insert-file-path-&name-here**
fastboot oem reboot-recovery
STEPS USED TO FLASH Disable_Dm-Verity_ForceEncrypt
Download zip file from developers XDA page HERE
Code:
adb shell twrp wipe data
adb shell reboot recovery
adb push Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip /sdcard/Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip
adb shell twrp install /sdcard/Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip
STEPS USED TO SIDELOAD MAGISK
Download from Developers GitHub repo HERE
I had trouble with the newest V20. Stay on tested version V19.2, unless you can troubleshoot problems on your own.
Code:
adb shell twrp sideload
adb sideload C:\Users\(your user name HERE)\Downloads\Magisk-v19.2.zip
Device tree used
https://github.com/mrmazakblu/Bold-N1_minimum_device
Kernel source
https://github.com/mrmazakblu/Bold-N1-Kernel.git
Released twrp folder on android file host HERE
Stock recovery image HERE
.
Call for help
@vampirefo ,you had fixed touchscreen issue in recovery on other devices. You also helped me to do the same too. If you find some time , could you try point me in some direction.
mrmazak said:
@vampirefo ,you had fixed touchscreen issue in recovery on other devices. You also helped me to do the same too. If you find some time , could you try point me in some direction.
Click to expand...
Click to collapse
No luck with decrypting here
Tried to backup stock recovery with no luck. Do u have a copy ?
greeneyez15o said:
No luck with decrypting here
Tried to backup stock recovery with no luck. Do u have a copy ?
Click to expand...
Click to collapse
How did you try to backup stock recovery?
Yes do have stock images loaded on filehost as well. I will add a link in the OP.
Let's try and figure out why you had trouble decrypt.
Start by flashing that twtp image to recovery. Boot I to the twrp then follow the steps I listed
mrmazak said:
How did you try to backup stock recovery?
Yes do have stock images loaded on filehost as well. I will add a link in the OP.
Let's try and figure out why you had trouble decrypt.
Start by flashing that twtp image to recovery. Boot I to the twrp then follow the steps I listed
Click to expand...
Click to collapse
Not sure, but now Im bootlooping to twrp :/
greeneyez15o said:
Not sure, but now Im bootlooping to twrp :/
Click to expand...
Click to collapse
do you know if your phone had received the ota update. there was an update made on
Wednesday, 16-Oct-19 03:27:28 UTC not sure when it was released, though.
it is possible, but unconfirmed that this update may have made this bootloop happen. because others have said that the update made them loose there root. Unknown about the unlock status
I am still trying to fix this twrp, as it is still only one I have seen.
I also have a different phone(umidigi F1) with same soc, mt6771.
A Dev made twrp for that device that even works decrypt. @PeterCxy.
I have forked his build tree. And am trying to copy his success. Unfortunately even though devices have same soc, the encryption method is different enough that the files used to make decrypt work on F1 are not present on N1.
A made a full firmware dump of the N1 at
https://github.com/mrmazakblu/blu_n0030ww_dump
working on porting , then building old Carliv touch recovery. since it can be used with the volume rocker as well as touch.
So far i have it ooting and adb works. Of course with device encrypted , the internal storage is not accessed. but once i get the fsab and vold correctly mapped, it will be ok.
am not posting the port till sdcard is fixed, and can be built from source.
sounds great man i just oem unlocked the bold n1 how do i go far as rooting wise without the custom recovery. using magisk or do i gotta wait until the carliv recovery is available
dxpeboiiii said:
sounds great man i just oem unlocked the bold n1 how do i go far as rooting wise without the custom recovery. using magisk or do i gotta wait until the carliv recovery is available
Click to expand...
Click to collapse
Well it's up to you. In this thread I have detailed how I used ADB with twrp to flash first decrypt install package, then magisk. Or you can patch boot.img with magisk manager then flash back to phone with fastboot or sp-flash tool.
Or if you are going to use gsi AOSP, you don't need any of these options.
Any word on the touch twrp. Im rooted with magisk but need viper4android and cant seem to flash properly without twrp... I tryed all kinds of ways
dxpeboiiii said:
Any word on the touch twrp. Im rooted with magisk but need viper4android and cant seem to flash properly without twrp... I tryed all kinds of ways
Click to expand...
Click to collapse
Did you try either of the 2 ways I explained how to use adb to install zips?
1- adb sideload
2- adb twrp install. Xzxsome-zip-name
But I thought viper4android has not worked on devices higher than marshmallow
I gotten it to work on my galaxy tab a on Oreo and my galaxy s7 and different varieties of devices. And yes i tryed the command from abd in twrp to install zip.. no success yet. BUT i have a otg from a samsung devices. And am able to use twrp within the mouse and keyboard. So tryna see what my options are as far as installin zips
dxpeboiiii said:
I gotten it to work on my galaxy tab a on Oreo and my galaxy s7 and different varieties of devices. And yes i tryed the command from abd in twrp to install zip.. no success yet. BUT i have a otg from a samsung devices. And am able to use twrp within the mouse and keyboard. So tryna see what my options are as far as installin zips
Click to expand...
Click to collapse
That's good, lets us know how the otg mouse works out. I did not have one to try it.
I got viper4android workin .. i downloaded a module called "Magisk SELInux permissive Script" this basically gave me the option to be permissive thats need for viper to work. And busybox but im pretty sure thats already installed from magisk but if not just install busybox. Should be good to go for audio mods?? bout to try dolby now.. let you kno how it goes
Basically i have the device unencrypted and under magisk settings you wanna uncheck "magisk hide" you will fail safety thing but me personally idc. But anyway follow the above comment along with wat i just said you should have no issues installin viper and dolby. I also recommend a otg for custom recovery. Just easier in my opinion. I basically got device setup how i want and backed it up thru twrp. But any question feel free to ask. More then welcome to help anybody .
deleted.
dml0211 said:
deleted.
Click to expand...
Click to collapse
I think you posted in wrong stop. I see you deleted before I got reply. Oh well.
But if you need to know which type of gsi to use on your device. The best bet is to use this app, from play store.
https://play.google.com/store/apps/details?id=tk.hack5.treblecheck
mrmazak said:
@vampirefo ,you had fixed touchscreen issue in recovery on other devices. You also helped me to do the same too. If you find some time , could you try point me in some direction.
Click to expand...
Click to collapse
I got to fix the touch issue. After a bit of debugging I figured out that kernel is not able to find the firmware file for goodix:
Code:
[ 0.935177] (4)[222:goodix-parse_cf]goodix_i2c 0-005d: Direct firmware load for goodix_cfg_group.bin failed with error -2
[ 0.935177] (5)[1:swapper/0]BOOTPROF: 935.177078:probe: probe=i2c_device_probe drv=goodix_i2c(ffffff80097f7b08) 77.446154ms
[ 0.935191] (5)[1:swapper/0]i2c i2c-0: Failed to register i2c client cap_touch at 0x5d (-16)
[ 0.935191] (4)[222:goodix-parse_cf]goodix_i2c 0-005d: Falling back to user helper
[ 0.935204] (5)[1:swapper/0]i2c i2c-0: of_i2c: Failure registering /[email protected]/[email protected]
...
...
[ 2.422885] (7)[222:goodix-parse_cf]goodix_i2c 0-005d: Direct firmware load for goodix_cfg_group.bin failed with error -2
[ 2.422892] (7)[222:goodix-parse_cf]goodix_i2c 0-005d: Falling back to user helper
[ 2.423524] (4)[321:ueventd]ueventd: firmware: loading 'goodix_cfg_group.bin' for '/devices/platform/11007000.i2c/i2c-0/0-005d/firmware/goodix_cfg_group.bin'
[ 2.423633] (4)[321:ueventd]ueventd: firmware: could not find firmware for goodix_cfg_group.bin
[ 2.423664] (4)[321:ueventd]ueventd: loading /devices/platform/11007000.i2c/i2c-0/0-005d/firmware/goodix_cfg_group.bin took 0ms
[ 2.423695] (7)[222:goodix-parse_cf][GTP-ERR][goodix_read_cfg_bin:493] Cfg_bin image [goodix_cfg_group.bin] not available,error:-11, try_times:2
I digged in deeper an figured out that the firmware files are in /vendor/firmware folder and and I extracted it out and put it in
Code:
recovery/root/etc/firmware
and touch works as a result.
Code:
adb pull /vendor/firmware/goodix_cfg_group.bin
BTW, I have not yet figured out the reason for delayed screen on. I am debugging that and will let you know if I get some leads. I am also not able to get the decrypt working as of now.
Please let me know if you need any more details about how to get the touch working.
vineethrp said:
I got to fix the touch issue. After a bit of debugging I figured out that kernel is not able to find the firmware file for goodix:
Code:
[ 0.935177] (4)[222:goodix-parse_cf]goodix_i2c 0-005d: Direct firmware load for goodix_cfg_group.bin failed with error -2
[ 0.935177] (5)[1:swapper/0]BOOTPROF: 935.177078:probe: probe=i2c_device_probe drv=goodix_i2c(ffffff80097f7b08) 77.446154ms
[ 0.935191] (5)[1:swapper/0]i2c i2c-0: Failed to register i2c client cap_touch at 0x5d (-16)
[ 0.935191] (4)[222:goodix-parse_cf]goodix_i2c 0-005d: Falling back to user helper
[ 0.935204] (5)[1:swapper/0]i2c i2c-0: of_i2c: Failure registering /[email protected]/[email protected]
...
...
[ 2.422885] (7)[222:goodix-parse_cf]goodix_i2c 0-005d: Direct firmware load for goodix_cfg_group.bin failed with error -2
[ 2.422892] (7)[222:goodix-parse_cf]goodix_i2c 0-005d: Falling back to user helper
[ 2.423524] (4)[321:ueventd]ueventd: firmware: loading 'goodix_cfg_group.bin' for '/devices/platform/11007000.i2c/i2c-0/0-005d/firmware/goodix_cfg_group.bin'
[ 2.423633] (4)[321:ueventd]ueventd: firmware: could not find firmware for goodix_cfg_group.bin
[ 2.423664] (4)[321:ueventd]ueventd: loading /devices/platform/11007000.i2c/i2c-0/0-005d/firmware/goodix_cfg_group.bin took 0ms
[ 2.423695] (7)[222:goodix-parse_cf][GTP-ERR][goodix_read_cfg_bin:493] Cfg_bin image [goodix_cfg_group.bin] not available,error:-11, try_times:2
I digged in deeper an figured out that the firmware files are in /vendor/firmware folder and and I extracted it out and put it in
Code:
recovery/root/etc/firmware
and touch works as a result.
Code:
adb pull /vendor/firmware/goodix_cfg_group.bin
BTW, I have not yet figured out the reason for delayed screen on. I am debugging that and will let you know if I get some leads. I am also not able to get the decrypt working as of now.
Please let me know if you need any more details about how to get the touch working.
Click to expand...
Click to collapse
Thank you. I added the firmware to the recovery ramdisk and repacked. Just like you said. Now I have touch working. THis may have re-sparked my interest. I have more to work with now. Thanks.
Perhaps twrp is not properly mounting the /vendor and this is why we need to add that bin file to recovery/root. May also be same issue making the screen on time lag. Either way this seems like a big step forward.
I am working on adding the goodix firmware to the device tree I am building with, so will not need to do repacking. I have added the test build with working touch to the file host folder linked in OP
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.
Hey guys, i present you one of my biggest projects so far:
LiteE RN10S Global!!!
This is probably the first MIUI mod for this device, althought it might not be the FIRST ROM, it's the FIRST MIUI MOD without that oversharpening effect. Keeping color schemes and everything working!
FEATURES:
Heavily Debloated
MIUI Dialer, contacts and messages (still uses google dialer for calling)
Removed a ton of tracers
Bootanimation from MIUI 12.5
Uses the chinese variant of Security Center and Miui Gallery
Mi Wallpaper with super wallpaper options
Voice Changer
Chinese Alpha Launcher
High-end icon animations
Genom Kernel by rama982 (on telegram)
and most importantly:
NO OVERSHARPENING!!! (don't worry i didn't delete PQ)
BUGS:
Mirror app doesn't work.
You tell me.
FIXES:
Reverted the MiuiAod for more stability
Added the Backup app back
Added the Mi Sound app back.
NOTES:
First boot may be laggy, don't worry, just set it up, and reboot.
CREDITS:
myst33d (on tg), for helping me a lot.
rama982 (on tg), for genom kernel.
@el0xren, for telling me about the app permissions.
And everyone else.
DOWNLOAD LINK:
Google Drive
Others will come soon.
KERNEL SOURCE: Here
ok but, how do we flash it?
REQUIREMENTS:
1. Unlocked bootloader.
2. Fastboot Drivers.
3. A brain.
Step by step:
1. Download the ROM, after it's done, extract it.
2. Rename the folder "LiteE". Nothing else.
3. Put your phone into fastboot mode, and execute the .sh (if you're on linux) or .bat (if you're on windows).
4. Wait until it finishes flashing, it will automatically reboot and close.
5. You're done!
ESPERIMENTAL:
There might be a way to flash this Mod without losing data. However this is not tested.
You need to already have MIUI Global 12.5.14 installed.
1. Same steps from before, but this time, execute the "flasher_no_userdata_md_udc" file.
Telegram Chats:
Support Group: https://t.me/LiteEDevelopmentGroup
Channel: https://t.me/LiteEDevelopmentChannel
Changelog:
- 1.3:
Working Mi Dialer with call recorder
New charging animation
Deodexed
Fixed flasher issue
I forgot
- 1.2.5:
Changelog in telegram
- 1.2:
MIUI Dialer, contacts and messages (still uses google dialer for calling)
Bootanimation from MIUI 12.5
Uses the chinese variant of Security Center and Miui Gallery
Chinese Alpha Launcher
High-end icon animations
- 1.1:
Never published on XDA
Added the vbmeta patcher in flasher script (this fixes that cannot boot into userspace error)
Changed boot sound and boot animation from Redmi Note 9T
MIUI Launcher Mod by Sipollo (removed)
High-end icon animations
Chinese version of Search (removed)
App Vault from MIUI 13 (removed)
Uses the chinese version of Mi Calendar (removed)
- 1.0:
Initial release
Wow nice., Hoping for more upcoming custom rom for our handset. Thanks
J6idot said:
Hey guys, i present you one of my biggest projects so far:
LiteE RN10S Global!!!
This is probably the first MIUI mod for this device, althought it might not be the FIRST ROM, it's the FIRST MIUI MOD without that oversharpening effect. Keeping color schemes and everything working!
FEATURES:
Heavily Debloated
Removed a ton of tracers
More colorful bootanimation
Uses the chinese variant of File Explorer, Security Center and Miui Gallery
Mi Wallpaper with super wallpaper options
Custom MiuiAod with "always on" function
Voice Changer
Genom Kernel by rama982 (on telegram)
and most importantly:
NO OVERSHARPENING!!! (don't worry i didn't delete PQ)
BUGS:
I have no idea how to test the Voice Changer function. Could anyone try this?
You tell me.
NOTES:
First boot may be laggy, don't worry, just set it up, and reboot.
CREDITS:
myst33d (on tg), for helping me a lot.
rama982 (on tg), for genom kernel.
@el0xren, for telling me about the app permissions.
And everyone else.
DOWNLOAD LINK:
Google Drive
Others will come soon.
KERNEL SOURCE: Here
ok but, how do we flash it?
REQUIREMENTS:
1. Unlocked bootloader.
2. Fastboot Drivers.
3. A brain.
Step by step:
1. Download the ROM, after it's done, extract it.
2. Rename the folder "LiteE". Nothing else.
3. Put your phone into fastboot mode, and execute the .sh (if you're on linux) or .bat (if you're on windows).
4. Wait until it finishes flashing, it will automatically reboot and close.
5. You're done!
ESPERIMENTAL:
There might be a way to flash this Mod without losing data. However this is not tested.
You need to already have MIUI Global 12.5.14 installed.
1. Same steps from before, but this time, execute the "flasher_no_userdata_md_udc" file.
Telegram Chats:
Support Group: not yet
Channel: https://t.me/LiteEDevelopmentChannel
Click to expand...
Click to collapse
big big work
Wow, Great work. Thanks. But is genome karnel stable?
Awesome work, might try it later
IamAlaminislam said:
Wow, Great work. Thanks. But is genome karnel stable?
Click to expand...
Click to collapse
yep
I can't seem to find the telegram channel for the genome karnel. Want to know the change log..
Can this work as a daily driver ROM? If anyone can post screenshots?
I had lost all hopes and already was planning to sell my 4 month old note10s.
If this can work as a daily driver ROM, I would keep the otherwise awesome device.
GildroY said:
Can this work as a daily driver ROM? If anyone can post screenshots?
I had lost all hopes and already was planning to sell my 4 month old note10s.
If this can work as a daily driver ROM, I would keep the otherwise awesome device.
Click to expand...
Click to collapse
why not? rom works perfectly fine
J6idot said:
why not? rom works perfectly fine
Click to expand...
Click to collapse
Thanks. Will try it out tonight
J6idot said:
why not? rom works perfectly fine
Click to expand...
Click to collapse
Getting the following error:
Code:
~/mnt/crucial/data/Phone/Note 10s/LiteE$ ./flasher.sh
product: secret
Step 1
Sending 'boot_a' (34128 KB) OKAY [ 1.233s]
Writing 'boot_a' OKAY [ 0.125s]
Finished. Total time: 1.371s
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Sending sparse 'system' 1/21 (131064 KB) OKAY [ 3.708s]
Writing 'system' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
There was a problem flashing the system.img.
Stuck into fastboot mode post this error.
Has anyone faced this issue?
GildroY said:
Getting the following error:
Code:
~/mnt/crucial/data/Phone/Note 10s/LiteE$ ./flasher.sh
product: secret
Step 1
Sending 'boot_a' (34128 KB) OKAY [ 1.233s]
Writing 'boot_a' OKAY [ 0.125s]
Finished. Total time: 1.371s
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Sending sparse 'system' 1/21 (131064 KB) OKAY [ 3.708s]
Writing 'system' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
There was a problem flashing the system.img.
Stuck into fastboot mode post this error.
Has anyone faced this issue?
Click to expand...
Click to collapse
this problem again, i know how to fix it.
1. get the vbmeta file.
2. type in the terminal "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
3. Launch the installer again.
J6idot said:
this problem again, i know how to fix it.
1. get the vbmeta file.
2. type in the terminal "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
3. Launch the installer again.
Click to expand...
Click to collapse
Will try again tonight post work. Many thanks.
J6idot said:
this problem again, i know how to fix it.
1. get the vbmeta file.
2. type in the terminal "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
3. Launch the installer again.
Click to expand...
Click to collapse
Worked like a charm!!
Thanks a ton.
In this rom i am randomly get a "green screen" when held the phone. Only reboot can resolve this. I think a custom kernel do this. And don't work stock miui phone with call recorder, only Google phone and so. No perfect for me.
angel495 said:
In this rom i am randomly get a "green screen" when held the phone. Only reboot can resolve this. I think a custom kernel do this. And don't work stock miui phone with call recorder, only Google phone and so. No perfect for me.
Click to expand...
Click to collapse
yes yes, i already know about that green screen problem. The reason this happens is because of the custom MiuiAod. I will revert this in the next build.
And no, i'm not going to add miui dialer
J6idot said:
yes yes, i already know about that green screen problem. The reason this happens is because of the custom MiuiAod. I will revert this in the next build.
And no, i'm not going to add miui dialer
Click to expand...
Click to collapse
Iam flash your rom over Indonesian where be miui phone and etc., And they stop working. I need call record and working aod. Can we solve this issue? And on stock rom phone does not go in to the deep sleep, then screen is off, cpu continue work on low frequency... How about this rom? (can see a battery chart?)
angel495 said:
Iam flash your rom over Indonesian where be miui phone and etc., And they stop working. I need call record and working aod. Can we solve this issue? And on stock rom phone does not go in to the deep sleep, then screen is off, cpu continue work on low frequency... How about this rom? (can see a battery chart?)
Click to expand...
Click to collapse
ok so, miui dialer isn't going to work on global rom, and for aod use the one from stock firmware. I do not have it right now.
J6idot said:
ok so, miui dialer isn't going to work on global rom, and for aod use the one from stock firmware. I do not have it right now.
Click to expand...
Click to collapse
Can you get advise about make a change for in system and vendor folder (its write protect)... I am try edit a build.prop file, but then i save changes file just gone and i need make a reflash.
angel495 said:
In this rom i am randomly get a "green screen" when held the phone. Only reboot can resolve this. I think a custom kernel do this. And don't work stock miui phone with call recorder, only Google phone and so. No perfect for me.
Click to expand...
Click to collapse
J6idot said:
ok so, miui dialer isn't going to work on global rom, and for aod use the one from stock firmware. I do not have it right now.
Click to expand...
Click to collapse
For call recording you can use axet's call recorder. It's available on fdroid and is working fine so far, for me, with this rom.