[RECOVERY][TB-X505F][UNOFFICIAL] TWRP 3.6.x for Lenovo Tab M10 HD

Search This thread

Transi

Senior Member
Aug 31, 2009
60
2
sorry recovery menü. my lenovo tab m10 tb-x505f crashed and I can only get into Fastboot and Recovery, Windows recognizes the tablet in Fastboot Mode and Recovery, ADB does not recognize the tablet, I also get no Enable USB debugging, how do I get I use Fastboot Mode and Recovery Mode Enable USB debugging?
 

alecxs

Forum Moderator
Staff member
Feb 17, 2016
3,754
5
1,724
gitlab.com
you don't need adb or authorize fastboot. only install Android Bootloader Interface drivers.
 

Transi

Senior Member
Aug 31, 2009
60
2
I installed all drivers, every mode of Windows is recognized. QcomDLoader_1.3.2.0 doesn't want the rawprogram_upgrade.xml from ROM Lenovo_Tab_M10_HD_TB-X505F_HW70_S001035_1912310946_Q00015_ROW_QDL
 

alecxs

Forum Moderator
Staff member
Feb 17, 2016
3,754
5
1,724
gitlab.com
every mode? you say you can only get into fastboot mode and recovery mode. now you're interested in EDL mode? that requires Qualcomm HS-USB QDLoader 9008 drivers, unrelated to the other modes/drivers.

not sure how that fits in this thread...

edit: seems you're talking to montolla
Hello


The only tool that work for me on the dead/breack tablet tb-x505f was Qfil/Qpst with stock formware that have a file and two xml files that the tool needs. Since the device was dead, O did open the back cover, remove battery and make a jump between to point nearby, then conect the cable and the device enter in dmg mode or something lile that, then the flash process begin.

If you have access to twrp, there is a reboot option to enter that mode wothout o0en the tablet.



Thanks

but why would you do that? you can flash more comfortable in fastboot mode (except bootloader is locked, you can't install TWRP in that case)
 
Last edited:

Transi

Senior Member
Aug 31, 2009
60
2
bootloader is locked
bootloader unlocked without USB debugging?
 
Last edited:

Yahoo Mike

Senior Member
Apr 3, 2011
459
208
Tamworth
sorry recovery menü. my lenovo tab m10 tb-x505f crashed and I can only get into Fastboot and Recovery, Windows recognizes the tablet in Fastboot Mode and Recovery, ADB does not recognize the tablet, I also get no Enable USB debugging, how do I get I use Fastboot Mode and Recovery Mode Enable USB debugging?
If you have stock recovery, select "power off". Then use Lenovo's LMSA tool to restore stock ROM. Note: this will wipe all your data on the tablet.
 

Yahoo Mike

Senior Member
Apr 3, 2011
459
208
Tamworth
New version of twrp in the OP.

The TW_EXTRA_LANGUAGES flag has been set and the latest TB_X505F_S001149_221115_ROW kernel injected. Thanks to @Tonyha7 for the changes. Languages like Chinese, Japanese and Korean should now be available.
 

harvey

Senior Member
Jan 21, 2006
63
13
Hi, i have TB_X505F_S001149_221115_ROW and just installed twrp 3.7 and newest Magisk. But now i cant go into system. After boot i'm allways back to twrp. Fastboot is also possible, but no more.
Any Ideas? Thanks
-------------
OK got it. Downloaded the same stockfirmware with the rescue-assistent from lenovo, but the rescue in edl-mode didnt work- gives error after 80%. Maybe because i tried it in Virtualbox on a linuxsystem, but i have no native win anymore.

So i flashed original recovery, vendor and system with fastboot and make a factory-reset in stock recovery. After reboot i did a quick install without network, installed magisk. Magisk telled me, it would allways be installed (ok, new boot.img i didnt flash), so i let it make the things necessary and reboot. Activated developer settings, usb-debugging (didnt know whether this was necessary at this point) and flashed twrp_3.7 again.
After reboot system works, also twrp and root.

Thanks for custom-recovery.
 
Last edited:

uschipower

Senior Member
Mar 14, 2009
77
4
since my last post here in this thread in 11.2022, Lenovo released another ROM for TB-X505F
In November, latest ROM was TB_X505F_S001147_220830_ROW.
Now, LRSA offers TB_X505F_S001149_221115_ROW

At the moment, I have a clean TB-X505F with TB_X505F_S001149_221115_ROW installed with LRSA. Bootloader is still unlocked.
But my latest TWRP-Backup was made with Stock-Rom < TB_X505F_S001147_220830_ROW --> with your TWRP 3.6

How can I use this Backup to Restore Apps, Settings, etc. in the new Rom?

I also noticed that OTA-Updates from Lenovo do not work if Rom has been modified (TWRP + Magisk). If I flash an older rom + twrp 3.6, it is not possible to update the rom, right?
 

Yahoo Mike

Senior Member
Apr 3, 2011
459
208
Tamworth
since my last post here in this thread in 11.2022, Lenovo released another ROM for TB-X505F
In November, latest ROM was TB_X505F_S001147_220830_ROW.
Now, LRSA offers TB_X505F_S001149_221115_ROW

At the moment, I have a clean TB-X505F with TB_X505F_S001149_221115_ROW installed with LRSA. Bootloader is still unlocked.
But my latest TWRP-Backup was made with Stock-Rom < TB_X505F_S001147_220830_ROW --> with your TWRP 3.6

How can I use this Backup to Restore Apps, Settings, etc. in the new Rom?

I also noticed that OTA-Updates from Lenovo do not work if Rom has been modified (TWRP + Magisk). If I flash an older rom + twrp 3.6, it is not possible to update the rom, right?
This post explains a little about why there are two versions of TWRP in the OP. Bottom line: if one doesn't work, try the other one.

And this post (and the other posts around it) might help with your OTA question.
 

uschipower

Senior Member
Mar 14, 2009
77
4
What is the exact error message you get when you try to restore backups?
No message.
I start with a clean TB_X505F_S001149_221115_ROW flashed with LRSA.
- Boot into Download-Mode
- flash your TWRP 3.7 with fastboot
- Boot into TWRP
- until now, everything is ok
- use Restore in TWRP (boot, system, data, misc)
- Restore without any Error-Messages
- Then restart, but now I can neither boot into Recovery nor in System

Which Partitions should i restore from backup, which not?
 

alecxs

Forum Moderator
Staff member
Feb 17, 2016
3,754
5
1,724
gitlab.com
boot, system, (vendor?) is ROM. misc, fota, cache, para are just trash partitions were android stores temporary instructions or some settings (although I have seen devices where misc contains important data such as imei?)

all other partitions is firmware, such as efs, nvram, modem, audio, display...

userdata is the only partition that is writeable to user. but you can't restore backup of userdata that has its origin of different ROM (at least not
for major versions)

Note: stock ROM won't boot along with TWRP installed, unless patched against avb/dm-verity.
 
Last edited:

uschipower

Senior Member
Mar 14, 2009
77
4
boot, system, vendor is ROM.
all other partitions is firmware, such as efs, nvram, modem, audio, display...

userdata is the only partition that is writeable to user. but you can't restore backup of userdata that has its origin of different ROM (at least not
for major versions)

At the moment, I have a clean installation of newer rom than in the backup.
Which Partitions should I restore, and which partitions should i keep from newer rom?

You said that I can not mix partitions from different roms. So I have to restore boot, system and userdata together.
What about other partitions?

Is there a way to find out from TWRP-Backup-Files which rom-version was installed when I made the backup?


Note: stock ROM won't boot along with TWRP installed, unless patched against avb/dm-verity.

When I made the backup, of course there was TWRP-Recovery installed.

When I restore all Partitions (Recovery with twrp, boot, system, userdata), I read that I exactly have the status when I made the Backup.
Is this true? Do I have to patch against avb/dm-verity too?
 

alecxs

Forum Moderator
Staff member
Feb 17, 2016
3,754
5
1,724
gitlab.com
as I said, the only writeable partition is userdata. therefore only userdata should be restored.

if you restore system, you restore old ROM. if it's that what you want, then clean flash from LSMA was almost pointless.

dm-verity usually is patched in vbmeta, vendor or boot. if you have stock partitions, it should patched again, otherwise it will boot-loop
 
Last edited:

uschipower

Senior Member
Mar 14, 2009
77
4
if you restore system, you restore old ROM. if it's that what you want, then clean flash from LSMA was almost pointless.
ok, this would be case one. Which partitions should I restore for this case? You mentioned system. Of course userdata. What about boot, recovery, vendor, etc.?


as I said, the only writeable partition is userdata. therefore only userdata should be restored. dm-verity usually is patched in vbmeta, vendor or boot. if you have stock partitions, it should patched again, otherwise it will boot-loop
but you said that i cannot use userdata in other rom.
I am a little bit confused. Could you explain this, when it is possible and when not, and how to find out this. Thanks.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    New version of twrp is available on OP. It fixes the big fat juicy bug that crept in which corrupted backup/restore of the /data partition.

    I recommend you download the new twrp and make new backups.

    Any backups you have made with any versions of twrp for TB-X505F (from Dec 2021 onwards) might be corrupt.

    For those who care about the details: it was a one line change. The problem was with the fscrypt policy. In May 2021, v2 became default. The X505F uses v1. The incompatibility caused problems with backup/restore. The corrupt backups/restores did not abort due to this change (and similar).
    1
    should be disabled when you swipe to allow modifications on system.
    Is this the job of TWRP?
    Then, it seems that the TWRP in this thread is not doing this.

    dm-verity. that is patched in boot or vendor. you can find flashable zip for this.
    what do i have to look for?
    if I found a zip described as dmverity.zip is there a dependency to android version or something else?
  • 8
    This version of TWRP works on the Lenovo TB-X505F (wifi).

    For the TB-X505X, see this thread. For the TB-X605F/L, see this thread.

    For the TB-X606F/L, see this thread. The X606F/L is the second gen M10 and it uses a Mediatek SOC.

    Code:
    #include <std_disclaimer.h>
    /*
    * We are not responsible for bricked devices, dead SD cards,
    * thermonuclear war, or you getting fired because the alarm app failed. Please
    * do some research if you have any concerns about features included in this ROM
    * before flashing it! YOU are choosing to make these modifications, and if
    * you point the finger at us for messing up your device, we will laugh at you.
    */

    Working:
    AFAIK, everything is working including:
    • data decryption
    • MTP

    Known issues:
    • time not adjusting for Daylight Saving
    • OTA (for a workaround see this post)

    Before installing TWRP
    Before you install TWRP, upgrade your tablet to the Android 9 (Pie) or Android 10 (Q) stock ROM.

    This tablet shipped with Android 8 (Oreo), in which the bootloader did not allow unlocking. When you tried to unlock the bootloader, it gave this error message:
    Code:
    fastboot oem unlock-go
    FAILED (remote: 'unknown command')
    fastboot: error: Command failed

    Installation
    It is recommended that you also install Magisk. This will ensure TWRP remains your default recovery.

    Step-by-step guide

    1. download TWRP to your PC (see the Download section below)
    2. download magisk.apk to your MicroSD or OTG device. Get the latest Magisk apk file here. Rename the filetype from apk to zip (for example Magisk-v22.0.zip)
    3. 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
    4. flash the twrp image:
      Code:
      adb reboot bootloader
      fastboot flash recovery twrp.img
    5. 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
    6. 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.
    7. load Magisk (step two): flash Magisk. In TWRP:
      • select "Install"
      • use "select storage" to locate device you stored magisk.zip on.
      • press the OK button
      • select the Magisk zip file
      • swipe to confirm Flash
      • when Magisk is finished, hit the "Reboot System" button
    8. finished!

    If you prefer to use button combos, rather than fastboot/ADB commands:
    • Vol Down + Power = fastboot mode
    • Vol Up + Vol Down + Power = recovery mode

    Changelog
    Code:
    01/03/2023 - bug fix: data partition again backs up and restores correctly
    
    20/01/2023 - add TW_EXTRA_LANGUAGES and TB_X505F_S001149_221115_ROW kernel (credit to @Tonyha7 )
    
    30/12/2022 - add system partition to AdvancedWipe (TB_X505F_S001147_220830_ROW firmware only)
    
    15/11/2022 - TWRP 3.7.0-0 update
               - support for TB_X505F_S001147_220830_ROW
    
    18/12/2021 - TWRP 3.6.0-0 update
               - support for A12 decryption (keymaster)
    
    27/03/2021 - TWRP 3.5.1-0 update
               - change to landscape mode for tablets
    
    01/01/2021 - TWRP 3.5.0-0: initial release

    Downloads

    Source code

    Credits
    The guys at TeamWin Recovery Project.
    Everyone whose device trees I plagiarised from GitHub.

    Contributors
    Yahoo Mike
    Tonyha7


    Last Updated 2023-03-01 (fix /data backup/restore)
    Created 2021-01-01
    4
    I've updated the OP with a new version of twrp (v3.7.0). The new version will work with recent update (TB_X505F_S001147_220830_ROW). Thanks to @Roobeedoo , @SpaceCats and @uschipower for reporting the problem and testing this new version.

    The fix was a simple one. I just needed to update twrp with the kernel from TB_X505F_S001147_220830_ROW.

    In case this new twrp doesn't work with old versions of the stock ROM, I've put a link to the old twrp in the OP too.
    3
    There's a new image on the OP: twrp-X505F_11.img. It is version 3.6.0.

    This image should be compatible with Android 12. I haven't tested it on A12, only on stock ROM (A10). Let me know if there are any issues.
    2
    hey
    i able to install the twrp latest image .but i canot reboot into twrp.
    i tried the 3 key together methhod, but it keeps restarting.
    any idea what to do?
    thanks.
    "solved" i was able to load the twrp.
    after installation from cmd line, i had to take out the usb cable, and then press the 3 buttons.
    but now it is booting to twrp only, even after i wipe the system, it is still booting only to the twrp.
    is there any twrp rom i can try to install? i couldnt find any.
    please help!
    hi,
    i had the same problem, fixed by flashing also the boot not only the recovery.
    fastboot flash boot twrp.img
    fastboot flash recovery twrp.img
    work for me
    p.s
    be sure that you flash the correct system.img (i used Havoc-OS-v2.5-20190527-vvBuild-phhgsi_arm64_ab.img - work perfect)
    2
    Worked for me too - many thanks!
    Can't wait for a custom ROM!

    TWRP Recovery Installation Steps
    1. Download android platform tools
    2. Unlock developer mode on the M10
    3. Enable USB debugging on the M10
    3. OEM unlock enable on the M10
    4. XDA download TWRP copy to sd
    5. Download Magisk app (from Github!!! johnwu), change extension to .zip
    6. Adb to fastboot
    7. fastboot flash recovery [filename.img]
    8. Turn off device
    9. Turn on device holding all 3 buttons, release when see Lenovo splash screen
    10. In TWRP find Magisk zip
    11. Install Magisk

    Stock ROM Recovery
    1. Download qualcomm drivers 64 bit install
    2. Download Lenovo recovery and image tool windows app from Lenovo support website
    3. Fastboot oem edl
    4. Turn off M10
    5. Start recovery windows app, wait till instructions
    6. Hold volume up (up is the side of the button closest to the front camera) and insert cable
    7. Release button after windows app detects device
    8. Troubleshoot by checking windows device manager for the M10 appears as a Qualcomm device