Database Develop

[EDL][A2017/A2017U] Emergency DL Mode TWRP + Unlock + Upgrade

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
INTRODUCTION
I'm providing a set of files that allow you to unlock your bootloader or recover from the closest thing you can get to a hard brick.
MiFlash is capable of flashing anything to your phone while it is in Emergency Download mode.
Yes, this is voodoo magic and it works! Recover from any and all bricks! Some might call it necromancy.
However, it can be also be used even if the device is perfectly alright to simplify upgrading procedures and make ROM flashing fairly painless.
This is for A2017U (North America) and A2017 (China) models only! Do not attempt this on A2017G.
INSTRUCTIONS
If you are flashing TWRP on a locked bootloader, you must first enable OEM unlocking on your device.
You can do this by navigating to Settings -> About phone -> Tap "Build number" 7 times.
Now navigate to Settings -> Advanced settings -> Developer options -> Enable "OEM unlocking".
Follow the steps below with the FASTBOOT_UNLOCK package first, then go into fastboot mode and use the
"fastboot oem unlock" command to unlock (and wipe) your device. Download adb and fastboot below.
Install the Qualcomm QUSB_BULK drivers from below.
You should be able to simply extract them, then right click qcser.inf and press Install.
If you don't have this option, then use devmgmt.msc (Device Manager) to update the driver after entering EDL mode by
selecting manual install and browsing to the qcser.inf file there.
Once the drivers are installed, your device should be recognized as a COM port called "Qualcomm HS-USB QDLoader 9008".
Now install MiFlash (download below).
Open MiFlash and use the [select] button to select the A2017U_*_EDL folder package that you wish to flash.
Boot into EDL mode. (hold Volume Up + Volume Down + Power until you're stuck on a black screen)
Now just hit [flash] - watch the progress bars move and wait for the device row to turn green with flash complete!
If you are flashing TWRP, use the [Power] + [Volume Up] key combo to exit EDL mode and enter recovery. Release the keys when you see the ZTE logo.
You must have an unlocked bootloader to enter TWRP!
If the flash fails or is unable to communicate with the device, use the [Power] + [Volume Up] + [Volume Down] key combo to restart EDL mode.
Release the keys after 5 seconds then wait another 5 seconds before using the [refresh] or [flash] buttons on MiFlash.
EDL PACKAGES
FASTBOOT_UNLOCK
This will unlock all fastboot operations, including OEM unlock and fastboot boot/flash.
WARNING: Unlocking your bootloader will erase all userdata on the device! Your device will be completely reset to factory defaults!
Click here to download! (ZIP, 195.8 KiB)
B29_TWRP (Marshmallow 6.0)
This will install TWRP 3.0.4-1 and unlock fastboot operations while restoring B29 boot stack.
Click here to download! (ZIP, 59.4 MiB)
B15-NEW_TWRP (Nougat 7.0)
This will install TWRP 3.0.4-1 and unlock fastboot operations while restoring B15-NEW boot stack.
Click here to download! (ZIP, 60.6 MiB)
B15-NEW_FULL (Nougat 7.0)
This will install the entirety of the B15-NEW firmware and boot stack, including signed OEM system and boot. OTA capable and unlocks fastboot operations.
Click here to download! (ZIP, 2.4 GiB)
B19-NOUGAT_TWRP (Nougat 7.1.1)
This will install TWRP 3.0.4-1 and unlock fastboot operations while restoring B19-NOUGAT boot stack.
Click here to download! (ZIP, 61.0 MiB)
B19-NOUGAT_FULL (Nougat 7.1.1)
This will install the entirety of the B19-NOUGAT firmware and boot stack, including signed OEM system and boot. OTA capable and unlocks fastboot operations.
Click here to download! (ZIP, 2.4 GiB)
TOOLS
Xiaomi MiFlash Installer
Version: 2016.08.30.0
Click here to download! (MSI, 31.0 MiB)
Qualcomm QUSB_BULK Drivers
Version: 2.1.1.0 (2014-01-25)
WHQL signed.
Once the drivers are installed, your device should be recognized as a COM port called "Qualcomm HS-USB QDLoader 9008".
Click here to download! (ZIP, 2.7 MiB)
ADB & Fastboot
Visit the SDK Platform Tools download page
Using this, you should safely be able to recover from any brick!
Once in TWRP, you can flash a full OTA or restore your backups and be on your way.
It is tested and working on Windows 10 64-bit.
All zips are signed with Android SignApk and can be verified with TWRP. (they won't install, just say it's not a valid zip after verifying)
A2017 (China) can use this to convert their phone to A2017U if they want. DO NOT flash on A2017G.
POSSIBLE ISSUES & SOLUTIONS
OTA update zips may fail in stock recovery even after flashing FULL EDL packages. This is because MiFlash does not erase blocks before writing the system image. You can run this command from TWRP terminal or adb shell to erase system partition before flashing the EDL package:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/system bs=272144
Once this is done, OTA zips should succeed in stock recovery after flashing a FULL EDL package.
CREDITS
This was based on the A2017 B07 EDL zip provided by @tenfar at this XDA thread.
HISTORY
2017-04-10 - Added B19-NOUGAT FULL and TWRP package
2017-02-11 - Added B15-NEW FULL signed OTA capable package
2017-02-11 - Added fastboot operation unlock package
2017-02-11 - Separated MiFlash, Qualcomm QUSB_BULK Driver, and EDL packages, removed 7z archives
2017-02-09 - Added B15-NEW TWRP package
2017-02-09 - Added B29 TWRP package

Any idea if this will work with Nougat or not?

neo4uo said:
Any idea if this will work with Nougat or not?
Click to expand...
Click to collapse
It will work on Nougat, however, you will end up on B29 bootloader. You'll need to flash B29 full and upgrade again.
I am having some weird issues with Nougat boot stack flashing + TWRP so I'll hold off on posting a B15-NEW version of this for now.
Update: You can now flash the B15-NEW TWRP package instead.

@jcadduono
N BootStack from LineageOS thread can be use for this if you want to give a try, instead of B29.
The stack is from a zip N file (I can't disclose right now) and is full N stack, minus Boot and System of course.
P.S. be advice that " keymaster.mbn " file flashes to " xlbbak " partition. Or just check the updater_script for N changes.

Situation: A2017U full stock in Nougat no unlocked bootloader, no root
Want to: Install LOS because i HATE this bullsh... called MIFAidonotknowWTF
Can i use this procedure to do that?
Thanks a LOT

So basically, MiFlash just lets you firehose in any file to a QualComm device from EDL mode? That's pretty handy.

I assume the TWRP image will only work on an unlocked bootloader device, right?
Then again, I don't see why a locked bootloader device would get in such a bricked state in the first place.

Snaptraks said:
I assume the TWRP image will only work on an unlocked bootloader device, right?
Then again, I don't see why a locked bootloader device would get in such a bricked state in the first place.
Click to expand...
Click to collapse
It is softbrickable by adb commands... I have one device in boot loop.

trying to wrap my head around this whole bootstack/fastboot issue we have with the a7.
So in theory one could use this tool and then unlock (or just have working fastboot) directly from b15?
Then download the bootstack from los thread and be good to go? Or would that bork fastboot again...
I think I am currently running b20 bootstack on b15 by flashing draken's unlock zip without issue (that I know of) but am considering flashing the N version from los thread.

This thing works, guys! OMGOMGOMG! :highfive::laugh:
My device was in a "heavily bricked" state. No LED light on connect and permanent EDL mode. I am now fully functional after trying EVERYTHING but this.

KwesiJnr said:
This thing works, guys! OMGOMGOMG! :highfive::laugh:
My device was in a "heavily bricked" state. No LED light on connect and permanent EDL mode. I am now fully functional after trying EVERYTHING but this.
Click to expand...
Click to collapse
Have fun! Nougat images are now up!

jcadduono said:
Have fun! Nougat images are now up!
Click to expand...
Click to collapse
Can you help me to do this from full stock nougat?
1) Enable "OEM UNLOCKING" under Developer Options
2) Flash with MIflash the "A2017U_B15-NEW_TWRP_EDL"
2) reboot to recovery (vol - and power)
3) fastboot oem unlock
4) reboot to TWRP
5) Flash LineajeOS and Gapps
thanks for your help

Altomugriento said:
Can you help me to do this from full stock nougat?
1) Enable "OEM UNLOCKING" under Developer Options
2) Flash with MIflash the "A2017U_B15-NEW_TWRP_EDL"
2) reboot to recovery (vol - and power)
3) fastboot oem unlock
4) reboot to TWRP
5) Flash LineajeOS and Gapps
thanks for your help
Click to expand...
Click to collapse
step 2.5) reboot to bootloader from recovery
step 4) wipe system in twrp
step 6) use the [Format Data] button on wipe page of twrp (lineageOS may not be compatible with your current encryption, this will wipe all your settings and internal storage)
and yes that's everything, I believe.

Sticky. Nuff said.
Dev is finally taking off on this phone, thanks to literally 4 or 5 key people. I was afraid I'd made a mistake purchasing instead of O+3, but has worked out well.
Thanks for all your help in your free time.

DrakenFX said:
@jcadduono
N BootStack from LineageOS thread can be use for this if you want to give a try, instead of B29.
The stack is from a zip N file (I can't disclose right now) and is full N stack, minus Boot and System of course.
P.S. be advice that " keymaster.mbn " file flashes to " xlbbak " partition. Or just check the updater_script for N changes.
Click to expand...
Click to collapse
Thanks buddy, that keymaster -> xblbak appears to have been my issue! So illogical.
I compiled applypatch and used that to apply the B29_TO_B15-NEW .p files to my B29 binaries so they should be nice and exact. (sha1 matches from updater-script)
I can provide a full B15-NEW verity/OTA update friendly package if somebody wants. Just let me know.

Flash Done.
But i can't join to TWRP, it just turn it self off.

Eroticus said:
Flash Done.
But i can't join to TWRP, it just turn it self off.
Click to expand...
Click to collapse
If you are not unlocked you now need to go to fastboot mode and unlock before you can enter TWRP.
If you just mean the screen is still black, you have to hold volume + power up after flashing until it starts up, then let go when you see the ZTE logo.

Hi @jcadduono
I'm about to get my A7 (A2017U version) in few days. Would you please advise which method/process/steps is the best to upgrade to stock, rooted and fastboot working N B15 build?
Thanks

khangozzy said:
Hi @jcadduono
I'm about to get my A7 (A2017U version) in few days. Would you please advise which method/process/steps is the best to upgrade to stock and rooted N B15 build?
Thanks
Click to expand...
Click to collapse
Look up a couple posts.

jcadduono said:
Have fun! Nougat images are now up!
Click to expand...
Click to collapse
Because it had been reported that this was impossible, or at least very difficult, I wanted to clarify whether this means people with locked bootloader running N can now unlock and install TWRP?

TWRP & MAGISK - Can not install twrp custom recovery or magisk ;-;

I have a Redmi 9 Lancelot with A partition only , bootloader unlocked and i installed twrp 3.4.1 unofficial image in platform-tools folder in my PC.
I connected the device to laptop and write:
adb reboot bootloader
fastboot flash recovery twrp.img
And
fastboot reboot
And went in soft brick (bootloop), i unbricked it with fastboot commands. But is it possible to install twrp recovery to install magisk on my phone?
*Sorry for grammar that is my first post and i am a beginer ((
*Also I had a backup soo didn't lose data
after that i tried to install magisk with no custom recovery:
1. Installed magisk version 22
2. get the boot.img (a time I soft bricked my phone Redmi 9 Lancelot bootloader unlocked) the boot.img its for the same MIUI version of my phone
3. copied the boot.img to downloads folder, installed magisc V 22, generated the patched magisk file (magisk_patched_JsCNt.img)
4. enabled USB debuging, USB instalation and USB security debug
5. opened the CMD as administrator in platform tools folder with magisk_patched_JsCNt.img in it
6. My device its only A partition i checked with an app from an another tutorial (yours)
and
wrote
adb devices
adb reboot bootloader
fastboot flash boot magisk_patched_JsCNt.img
fastboot reboot
7. device entered SOFT BRICK (bootloop) and i unbricked it with fastboot comands
8. PLS tell me what did I do wrong PLEASE.

I had the same problem and found that this is the only solution.
The twrp im using is from this website: https://unofficialtwrp.com/xiaomi-redmi-9-root-twrp-3-4-1/
1. Download latest miui rom https://xiaomifirmwareupdater.com/miui/lancelot/ (make sure its "fastboot", you will need the boot.img later).
2. Flash it with "mi flash tool". Then download the magisk apk from here: https://github.com/topjohnwu/Magisk/releases
3. In the .tgz miui rom file find boot.img and copy it to your phone (you will need to extract it).
4. Patch the boot.img with the magisk app and copy it to your pc (the patched boot.img should be in your downloads folder)
5. Put your phone into fastboot mode (adb reboot bootloader), and flash the patched boot.img and vbmeta.img (you can find vbmeta on the site with custom twrp) - fastboot flash boot magisk_patched-[...].img, fastboot flash vbmeta vbmeta.img
6. After this reboot your phone and you should have magisk with root access.
* 7. Now you can flash twrp recovery with app from play store "flashify", you`ll just need to give it root access.
Last step is just if you want the twrp for flashing anything else.
Done

hokkus_nhw said:
I had the same problem and found that this is the only solution.
The twrp im using is from this website: https://unofficialtwrp.com/xiaomi-redmi-9-root-twrp-3-4-1/
1. Download latest miui rom https://xiaomifirmwareupdater.com/miui/lancelot/ (make sure its "fastboot", you will need the boot.img later).
2. Flash it with "mi flash tool". Then download the magisk apk from here: https://github.com/topjohnwu/Magisk/releases
3. In the .tgz miui rom file find boot.img and copy it to your phone (you will need to extract it).
4. Patch the boot.img with the magisk app and copy it to your pc (the patched boot.img should be in your downloads folder)
5. Put your phone into fastboot mode (adb reboot bootloader), and flash the patched boot.img and vbmeta.img (you can find vbmeta on the site with custom twrp) - fastboot flash boot magisk_patched-[...].img, fastboot flash vbmeta vbmeta.img
6. After this reboot your phone and you shoul have magisk with root access.
* 7. Now you can flash twrp recovery with app from play store "flashify", you`ll just need to give it root access.
Last step is just if you want the twrp for flashing anything else.
Done
Click to expand...
Click to collapse
dude entered soft brick again

hokkus_nhw said:
I had the same problem and found that this is the only solution.
The twrp im using is from this website: https://unofficialtwrp.com/xiaomi-redmi-9-root-twrp-3-4-1/
1. Download latest miui rom https://xiaomifirmwareupdater.com/miui/lancelot/ (make sure its "fastboot", you will need the boot.img later).
2. Flash it with "mi flash tool". Then download the magisk apk from here: https://github.com/topjohnwu/Magisk/releases
3. In the .tgz miui rom file find boot.img and copy it to your phone (you will need to extract it).
4. Patch the boot.img with the magisk app and copy it to your pc (the patched boot.img should be in your downloads folder)
5. Put your phone into fastboot mode (adb reboot bootloader), and flash the patched boot.img and vbmeta.img (you can find vbmeta on the site with custom twrp) - fastboot flash boot magisk_patched-[...].img, fastboot flash vbmeta vbmeta.img
6. After this reboot your phone and you should have magisk with root access.
* 7. Now you can flash twrp recovery with app from play store "flashify", you`ll just need to give it root access.
Last step is just if you want the twrp for flashing anything else.
Done
Click to expand...
Click to collapse
and now i am unbricking my phone bro

Got the same issue, as op, but my Phone simply ignores my try to enter bootloader, both from adb and from physical buttons. Got bootloop yesterday with hardbrick, but managed to reflash it with Official miui 12.0.4 Lancelot software FROM 31st of March 2021 version. Still not being able to put twrp, pbrp to it, no matter if i do it with vbmeta, or without. Few different versions had need tried already (to twrp), but no success. Once or twice, at the very beginning (before reflashing Whole rom) i got into twrp, but after restart Phone opened Stock recovery instead of twrp and my next try of putting it back in Phone resulted in bootloop, ay lmao xD
I'm Not sure now, what to do? I remembered having the same issue back in my first tulip days, but I cannot resemble a solution to it anymore.
There are no Official twrp or pbrp for this model, could it be the issue?

buczek0711 said:
Got the same issue, as op, but my Phone simply ignores my try to enter bootloader, both from adb and from physical buttons. Got bootloop yesterday with hardbrick, but managed to reflash it with Official miui 12.0.4 Lancelot software FROM 31st of March 2021 version. Still not being able to put twrp, pbrp to it, no matter if i do it with vbmeta, or without. Few different versions had need tried already (to twrp), but no success. Once or twice, at the very beginning (before reflashing Whole rom) i got into twrp, but after restart Phone opened Stock recovery instead of twrp and my next try of putting it back in Phone resulted in bootloop, ay lmao xD
I'm Not sure now, what to do? I remembered having the same issue back in my first tulip days, but I cannot resemble a solution to it anymore.
There are no Official twrp or pbrp for this model, could it be the issue?
Click to expand...
Click to collapse
the dude from the service told me: "I tried with all methods, with Xiaomi flash tool too, just the manufacturers can repair it"
i got it hard bricked ;-;

Officer X said:
the dude from the service told me: "I tried with all methods, with Xiaomi flash tool too, just the manufacturers can repair it"
i got it hard bricked ;-;
Click to expand...
Click to collapse
if your phone is still bricked you can try what i did... https://forum.xda-developers.com/t/hardbricked-redmi-9-mt6769.4302829/ try this
NOTE : When you got this error from the photo, dw bcs yes you still cant boot but the fastboot is back like after that just boot into fastboot and reinstall the official miui rom using mi flash tool
If mi flash tool says Error or smth that means your bootloader locked, simply just unlock it again with miui unlock tool
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Stefy1337 said:
if your phone is still bricked you can try what i did... https://forum.xda-developers.com/t/hardbricked-redmi-9-mt6769.4302829/ try this
NOTE : When you got this error from the photo, dw bcs yes you still cant boot but the fastboot is back like after that just boot into fastboot and reinstall the official miui rom using mi flash tool
If mi flash tool says Error or smth that means your bootloader locked, simply just unlock it again with miui unlock tool
View attachment 5411139
Click to expand...
Click to collapse
Its ok now i have magisk, the ideea was that my PC (with redmi 9 drivers, mediatek drivers and adb and fastboot drivers), didnt see that the phone its connected in device manager (i found someone who fixed it)

[Root Guide] Lenovo tab m10 FHD PLUS TB-X606x

Hello everyone,
just got this tablet from my internet provider in bundle !
I found one or 2 post talking about root ( via twrp ) but here i report ( tested by myself ) another way to root your
TB-X606x without the need of installing TWRP ( well if you need it just use the other method )
I've root on this latest ROM TB_X606X_S300326_210720_BMP available on ( Rescue and Smart Assistant (LMSA)
DISCLAIMER as always.. " do it at your OWN risk , i won't be responsible if anything goes wrong, you might risk to brick your tablet "​
that said let's go :
1- let's reboot in fastboot mode
Code:
adb reboot booatloader
(if your m10 just restart without entering fastboot than just poweroff, after that keep press POWER + VOLUME DOWN )
2 - unlock your bootloader ( if you don't know how.. have a quick search ..)
Code:
fastboot oem unlock
( if this gives you this error : FAILED (remote: 'unknown command') than do this:
Code:
fastboot flashing unlock
is gonna ask you to press VOLUME UP to unlock
or Volume DOWN to NOT unlock
you press volume UP
3 -
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
( you find the empty vbmeta.img attached to this post )
4 -
Code:
fastboot flash boot boot.img
(you find the ALREADY patched BOOT.IMG for ROM TB_X606X_S300326_210720_BMP attached in this post )
BE AWARE .. if you are going to ROOT another ROM version of TB-X606x you need to get the original BOOT.IMG from the official rom( the exact same version your system is updated to ) and than PATCH IT with magisk !!!
5 -
Code:
fastboot reboot
that's it ! Your m10 FHD PLUS TB-X606x is ROOTED !!!
FILES INCLUDED :
Vbmeta_empty.img is the EMPTY vbmeta .. simply rename it vbmeta.img before flash it
vbmeta_ORIG.img is the ORIGINAL vbmeta of ROM TB_X606X_S300326_210720_BMP just in case you need it..!!!
magisk_patched_boot_TB_X606X_S300326_210720.img is the PATCHED BOOT.IMG(rename it like this for convenience )
always for ROM TB_X606X_S300326_210720_BMP
ORIG_boot_TB_X606X_S300326_210720.img is the original boot.img

[reserved]

Hello, thx. i have one problem. my device not react to reboot to fastboot mode. my pc send message: waiting to device.
pleas help me. thx

bazzilisek85 said:
Hello, thx. i have one problem. my device not react to reboot to fastboot mode. my pc send message: waiting to device.
pleas help me. thx
Click to expand...
Click to collapse
turn it off , wait few seconds than keep press POWER + VOLUME DOWN
it'll enter fastboot , now plug your cable and write fastboot devices
you'll see your device connected

bazzilisek85 said:
Hello, thx. i have one problem. my device not react to reboot to fastboot mode. my pc send message: waiting to device.
pleas help me. thx
Click to expand...
Click to collapse
Make sure you have the latest MTK usb drivers.

Postup funkční - potvrzuji.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

LiborCZ said:
Postup funkční - potvrzuji.View attachment 5416675
Click to expand...
Click to collapse
This forum is English only, try here:
Google Translate
Google's service, offered free of charge, instantly translates words, phrases, and web pages between English and over 100 other languages.
translate.google.com

simika said:
Hello everyone,
just got this tablet from my internet provider in bundle !
I found one or 2 post talking about root ( via twrp ) but here i report ( tested by myself ) another way to root your
TB-X606x without the need of installing TWRP ( well if you need it just use the other method )
I've root on this latest ROM TB_X606X_S300326_210720_BMP available on ( Rescue and Smart Assistant (LMSA)
DISCLAIMER as always.. " do it at your OWN risk , i won't be responsible if anything goes wrong, you might risk to brick your tablet "​
that said let's go :
1- let's reboot in fastboot mode
Code:
adb reboot booatloader
(if your m10 just restart without entering fastboot than just poweroff, after that keep press POWER + VOLUME DOWN )
2 - unlock your bootloader ( if you don't know how.. have a quick search ..)
Code:
fastboot oem unlock
( if this gives you this error : FAILED (remote: 'unknown command') than do this:
Code:
fastboot flashing unlock
is gonna ask you to press VOLUME UP to unlock
or Volume DOWN to NOT unlock
you press volume UP
3 -
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
( you find the empty vbmeta.img attached to this post )
4 -
Code:
fastboot flash boot boot.img
(you find the ALREADY patched BOOT.IMG for ROM TB_X606X_S300326_210720_BMP attached in this post )
BE AWARE .. if you are going to ROOT another ROM version of TB-X606x you need to get the original BOOT.IMG from the official rom( the exact same version your system is updated to ) and than PATCH IT with magisk !!!
5 -
Code:
fastboot reboot
that's it ! Your m10 FHD PLUS TB-X606x is ROOTED !!!
FILES INCLUDED :
Vbmeta_empty.img is the EMPTY vbmeta .. simply rename it vbmeta.img before flash it
vbmeta_ORIG.img is the ORIGINAL vbmeta of ROM TB_X606X_S300326_210720_BMP just in case you need it..!!!
magisk_patched_boot_TB_X606X_S300326_210720.img is the PATCHED BOOT.IMG(rename it like this for convenience )
always for ROM TB_X606X_S300326_210720_BMP
ORIG_boot_TB_X606X_S300326_210720.img is the original boot.img
Click to expand...
Click to collapse
Hello guys, I tried this method today and it work with my model. I live in India and here in India, TB x606v model is available. The above method works with my model and is successful in performing root. I just patched the boot.img of rom of my particular model. All the other process is same as mentioned. Thanks Simika.

The tarapstar said:
Hello guys, I tried this method today and it work with my model. I live in India and here in India, TB x606v model is available. The above method works with my model and is successful in performing root. I just patched the boot.img of rom of my particular model. All the other process is same as mentioned. Thanks Simika.
Click to expand...
Click to collapse
I'm glad I could help

Okay so guys, the above root method works for all models of Lenovo tab M10 FHD Plus. I have tested. However, those who are facing bootloop problem after flashing patched boot image and empty vbmeta image. You can do one thing is that get the device in fastboot mode(by pressing volume down and power button for 10seconds) then connect it to your computer/laptop. Now using fastboot commands flash the original vbmeta.img, boot.img, vendor.img, system.img, and cache.img . These files can be downloaded using the Lenovo rescue assistant for your model. Then enter fastboot reboot command and your device will start working again. If after few days of rooting your device face problem of bootloop, then do the above mentioned method and then flash the patched magisk image again. It will fix the problem.

Hello, Just picked up a X606F model. I haven't even connected it to the internet yet. I was wondering if the root persists over updates? Or should I update first? Presently I'm on TB-X606F_S300320_210716_BPM
thanks,
A-

alexacm said:
Hello, Just picked up a X606F model. I haven't even connected it to the internet yet. I was wondering if the root persists over updates? Or should I update first? Presently I'm on TB-X606F_S300320_210716_BPM
thanks,
A-
Click to expand...
Click to collapse
doesn't matter cause when you'll root by patching the latest rom, latest updates will be applied after rooting.

I used this method to Root my M10 FHD Plus ( TB-X606F ) a few months ago.
Now, I am attempting to update, but I cannot find the location of the OTA file for TWRP to install?
Any one offer any clues as to what folder it might be in ?
Or a link to some repo of Lenovo ROMs ?
Thanks in Advance !

Can I Install update if I have root without TWRP?
Have I must full OTA download and unpack, extract boot.img and patch it in Magisk?

simika said:
Hello everyone,
just got this tablet from my internet provider in bundle !
I found one or 2 post talking about root ( via twrp ) but here i report ( tested by myself ) another way to root your
TB-X606x without the need of installing TWRP ( well if you need it just use the other method )
I've root on this latest ROM TB_X606X_S300326_210720_BMP available on ( Rescue and Smart Assistant (LMSA)
DISCLAIMER as always.. " do it at your OWN risk , i won't be responsible if anything goes wrong, you might risk to brick your tablet "​
that said let's go :
1- let's reboot in fastboot mode
Code:
adb reboot booatloader
(if your m10 just restart without entering fastboot than just poweroff, after that keep press POWER + VOLUME DOWN )
2 - unlock your bootloader ( if you don't know how.. have a quick search ..)
Code:
fastboot oem unlock
( if this gives you this error : FAILED (remote: 'unknown command') than do this:
Code:
fastboot flashing unlock
is gonna ask you to press VOLUME UP to unlock
or Volume DOWN to NOT unlock
you press volume UP
3 -
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
( you find the empty vbmeta.img attached to this post )
4 -
Code:
fastboot flash boot boot.img
(you find the ALREADY patched BOOT.IMG for ROM TB_X606X_S300326_210720_BMP attached in this post )
BE AWARE .. if you are going to ROOT another ROM version of TB-X606x you need to get the original BOOT.IMG from the official rom( the exact same version your system is updated to ) and than PATCH IT with magisk !!!
5 -
Code:
fastboot reboot
that's it ! Your m10 FHD PLUS TB-X606x is ROOTED !!!
FILES INCLUDED :
Vbmeta_empty.img is the EMPTY vbmeta .. simply rename it vbmeta.img before flash it
vbmeta_ORIG.img is the ORIGINAL vbmeta of ROM TB_X606X_S300326_210720_BMP just in case you need it..!!!
magisk_patched_boot_TB_X606X_S300326_210720.img is the PATCHED BOOT.IMG(rename it like this for convenience )
always for ROM TB_X606X_S300326_210720_BMP
ORIG_boot_TB_X606X_S300326_210720.img is the original boot.img
Click to expand...
Click to collapse
you can make phone calls as root?

alexacm said:
Hello, Just picked up a X606F model. I haven't even connected it to the internet yet. I was wondering if the root persists over updates? Or should I update first? Presently I'm on TB-X606F_S300320_210716_BPM
thanks,
A-
Click to expand...
Click to collapse
after any Ota update you need to do the process again

Hello, I just d/l the latest OTA. When I try and install it, it fails and reboots. Any ideas?
thanks-

Hello. I can help someone, a friend has this tablet model, adb detects the name nicely, reset to the bootloader, then after typing the command to unlock it, nothing happens, the tablet is in the place, no message. I was doing root on samsung, on sony and I had no such problems. win 10 64x. drivers are, turn off the signature of drivers too,
What could be wrong ?

adek89 said:
Hello. I can help someone, a friend has this tablet model, adb detects the name nicely, reset to the bootloader, then after typing the command to unlock it, nothing happens, the tablet is in the place, no message. I was doing root on samsung, on sony and I had no such problems. win 10 64x. drivers are, turn off the signature of drivers too,
What could be wrong ?
Click to expand...
Click to collapse
Make sure you have the latest fastboot and MTK drivers.

Yahoo Mike said:
Make sure you have the latest fastboot and MTK drivers.
Click to expand...
Click to collapse
Hello, I visited this link, but the download of MTK Drivers doesn't start.

How To Guide [GUIDE][REALME 8i][NARZO 50] Unlock Bootloader Flash TWRP and Root [RMX3151][RMX3286]

Hi Guys!
Since there is no deeptest.apk available for our device to unlock bootloader, we came up with another method to unlock bootloader unofficially!
In this guide I'll tell you how to unlock bootloader, root with magisk and flash TWRP on your Realme 8i/Narzo 50 (RMX3151/RMX3286)
Code:
/*
* This Guide is tested and working
* However I am 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 unlocking and flashing TWRP
* before flashing it! YOU are choosing to make these modifications.
*/
1. UNLOCKING BOOTLOADER:
Requirements
PC or Laptop
Internet connection
Realme 8i/Narzo 50
USB cable
Working Brain
Take a backup of your data since it'll be wiped
Go to About phone > Version and tap build number 7 times
Go to Settings > advanced settings > Developer options and turn on OEM unlocking and USB debugging
STEPS
Install Python from windows store
Install USBDk
Download this and extract : https://github.com/bkerler/mtkclient/archive/refs/heads/main.zip
Download vbmeta and patched boot image (Download for your respective version) in copy to the mtkclient-main folder
Now open command prompt or powershell in that folder
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now type pip3 install -r requirements.txt and hit enter
Now type python mtk e metadata,userdata,md_udc hit enter - This command wipes data
Then power off your phone and hold both volume buttons and connect usb cable (DON'T LEAVE THE BUTTONS, KEEP THEM HOLDING THROUGHOUT THE PROCESS) - This boots device into BROM mode
Now type python mtk da seccfg unlock This will unlock the bootloader (If you face waiting for device issue then unplug the device and plug in the device again with holding volume buttons, also don't leave the buttons)
After this unplug your phone and turn it on (It'll show your device dm verity corrupted and first boot might take 20-25 mins, don't panic)
Now your bootloader is unlocked
Due to realme's limitations you still can't access fastboot after unlocking via this method
2. ROOTING YOUR DEVICE:
Install This Magisk apk
Now in pc type python mtk w boot,vbmeta boot.patched,vbmeta.img.empty hit enter
Then power off your phone and connect usb while holding both volume buttons (and don't leave them)
Now disconnect and reboot phone
Now open magisk
3. FLASHING TWRP RECOVERY:
Download TWRP - From here
Download and install Flashify app
Open Flashify and grant root permission
Select Recovery image and install the twrp you have downloaded
After flashing is done click reboot now or you can reboot to recovery via magisk app
"Congrats Now we have working TWRP in our Realme 8i/Narzo 50"
Credits:
Me (@pritish1998) for TWRP, Unlock and Flashing guide
B Kerler fot MTKClient
Rohit for testing
Stock boot Images (to revert root)
If you face any issues contact me here

Thanks for the detailed guide, hope we get kernel sources soon..

sany.svenson said:
Добрый вечер.А как теперь заблокировать загрузчик,подскажите пожалуйста.
Click to expand...
Click to collapse
English is required, you can use your native language too, adding it to your post.
Inside the tool is provided a README.md file with basic instructions and usage. To relock bootloader you can use python mtk xflash seccfg lock just be careful to not relock it while running custom binaries, you have to return completely back to stock prior to do that.

After using boot.img from this topic wifi is dead! Now I need original boot to patch it. My firmware is A20. Somebody help!

DimaS_EKB said:
After using boot.img from this topic wifi is dead! Now I need original boot to patch it. My firmware is A20. Somebody help!
Click to expand...
Click to collapse
The provided boot image is from A30... Why are u still using A20?

I didn't know about A20 or A30 or anything. You should have mentioined this! Better off dump user's own boot.img and patch it with magisk. Now I have problems. It is good that I've found A20 firmware but it was not easy, I've lost a lot of time to read about firmwares, patching etc.

DimaS_EKB said:
I didn't know about A20 or A30 or anything. You should have mentioined this! Better off dump user's own boot.img and patch it with magisk. Now I have problems. It is good that I've found A20 firmware but it was not easy, I've lost a lot of time to read about firmwares, patching etc.
Click to expand...
Click to collapse
Download stock boot image from here I've saved them https://mega.nz/folder/BvpwibLB#lDDAbRG5SMKS4ucdj1dELg
Also there is nothing to mention at the time of making this guide almost everyone was updated to A.30, but no problem now I've updated the link for all patched boot images

recovered, thanks
now I'm updating to A32
what's next?
download your patched boot image for A32? and that's all?

DimaS_EKB said:
recovered, thanks
now I'm updating to A32
what's next?
download your patched boot image for A32? and that's all?
Click to expand...
Click to collapse
Yes

pritish1998 said:
Yes
Click to expand...
Click to collapse
Sorry but it appears I cannot update. I tried original and modified boot.img, also I installed original recovery. It doesn't help. The phone downloads the A32 firmware, reboots and cannot start recovery mode to update the firmware.

DimaS_EKB said:
Sorry but it appears I cannot update. I tried original and modified boot.img, also I installed original recovery. It doesn't help. The phone downloads the A32 firmware, reboots and cannot start recovery mode to update the firmware.
Click to expand...
Click to collapse
Flash stock boot, vbmeta and recovery then format data then reboot

If I flash stock vbmeta it cannot boot. Is that ok? Should I erase data anyway?

DimaS_EKB said:
If I flash stock vbmeta it cannot boot. Is that ok? Should I erase data anyway?
Click to expand...
Click to collapse
Yes

pritish1998 said:
Yes
Click to expand...
Click to collapse
Format data

Thanks! Now everything works fine!

pritish1998 said:
Download stock boot image from here I've saved them https://mega.nz/folder/BvpwibLB#lDDAbRG5SMKS4ucdj1dELg
Also there is nothing to mention at the time of making this guide almost everyone was updated to A.30, but no problem now I've updated the link for all patched boot images
Click to expand...
Click to collapse
how to flash stock boot image?

bobongros said:
how to flash stock boot image?
Click to expand...
Click to collapse
python mtk w boot boot.img

pritish1998 said:
python mtk w boot boot.img
Click to expand...
Click to collapse
can i dm you? please help me my phone is bricked

bobongros said:
can i dm you? please help me my phone is bricked
Click to expand...
Click to collapse
How did your phone brick?

[RECOVERY][UNOFFICIAL][3.5.2] TWRP for Galaxy M21 [CWB1 and Above]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer:
I am 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 recovery before flashing it!
YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
I am not the developer.
Developer: @naz664
Changelog:
Spoiler: View
Changelog :-
- Souls recovery with latest A12 support (Jan 2023)
- Updated kernel
- This recovery won't work on older stock version
So don't flash this unless you are running latest jan 2023 stock rom
How to install?
Spoiler: ODIN (Windows)
Prerequisites: Samsung USB drivers, Odin v3.14.1
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Press the volume down + volume up button whilst the phone is connected to a pc to boot in download mode;;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol down + Bixby key + USB cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, factory reset data and redo from step 5!
Download TWRP.tar from download link below;
Open odin and place the TWRP.tar file in AP slot and press start. Once you press start, keep holding power and volume up button and the device will reboot to recovery mode.
* If you're coming from stock, go to "Wipe" > ""Format Data" > type "yes" to format data. If you skip this, Internal storage won't work in TWRP
Flash the encryption_disabler.zip from the link below to disable internal storage encryption and patch stock recovery restoration.
Additionally, flash TWRP_Bootlogo_patcher to patch warning screens when booting the device.
If you want to root, flash Magisk.
Spoiler: TWRP
If you're coming from other TWRP versions, download TWRP.img, reboot to recovery, tap Install > Install Image > Navigate to downloads folder > select TWRP.img > Select Recovery and swipe to confirm flash. Go to reboot and reboot to recovery and the changes will have taken place.
TWRP Source: GitHub
Credits:
Soul reaper
Nazim
Lmao
Max B
Darshana & Encrypted for testing
Important:
This version only works on the latest update of stock rom (M215FXXU3CWB1) and above. If you are running an older version, use the previous build of TWRP.
Download: Link

И что делать ?

w1nk1 said:
И что делать ?
Click to expand...
Click to collapse
Different device?

Hi Fredin friend,
I Recently upgraded SM-M215G device to OneUi5.1 (M215GDDS3CWD1-20230522142126) Binary 3 and TWRP (twrp-3-5-2-m21-v3-1-a12-tar)but anything I am flashing is either bootlooping or stuck on Rom Logo, I flashed (Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip) still only Rom Logo showing, how to boot the GSIs? Any help appreciated.

OldNoobOne said:
Hi Fredin friend,
I Recently upgraded SM-M215G device to OneUi5.1 (M215GDDS3CWD1-20230522142126) Binary 3 and TWRP (twrp-3-5-2-m21-v3-1-a12-tar)but anything I am flashing is either bootlooping or stuck on Rom Logo, I flashed (Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip) still only Rom Logo showing, how to boot the GSIs? Any help appreciated.
Click to expand...
Click to collapse
Hi
If you had unencrypted data (if you could see files in internal storage) and flashed the latest stock rom, but you didn't flash encryption/multi disabler before the first boot into OneUI, it will probably cause problems.
So try formatting data and flash encryption/multi disabler (although I believe dm verity disabler also disables encryption by default, but it won't hurt flashing them). Or you can format data and not flash anything to let data stay encrypted, but then you won't be able to use the internal storage in TWRP.

Fredin_ said:
Hi
If you had unencrypted data (if you could see files in internal storage) and flashed the latest stock rom, but you didn't flash encryption/multi disabler before the first boot into OneUI, it will probably cause problems.
So try formatting data and flash encryption/multi disabler (although I believe dm verity disabler also disables encryption by default, but it won't hurt flashing them). Or you can format data and not flash anything to let data stay encrypted, but then you won't be able to use the internal storage in TWRP.
Click to expand...
Click to collapse
Hi friend Fredin,
Thanks for the reply.
I used (twrp-3-5-2-m21-v3-1-a12-tar) and it is smooth (just like previous Soulr-A11 twrp) but sideload did not work while the other recovery (TWRP.3.7.0_11.-.M215FXXU3CWB1.tar) by Dev Ravindu Deshan works great too but Reboot to Recovery does not work properly all the time, so sometimes instead of Reboot to Recovery the changes happen when manually reboot to recovery using usb cable also sometimes it does not recognise pen drive. Till now I only managed to boot Tuki1.2 and the other Lineage 20 zip had Oplist error 1 issue. Hoping for GSI boot too later. Thanks for recovery

OldNoobOne said:
Hi friend Fredin,
Thanks for the reply.
I used (twrp-3-5-2-m21-v3-1-a12-tar) and it is smooth (just like previous Soulr-A11 twrp) but sideload did not work while the other recovery (TWRP.3.7.0_11.-.M215FXXU3CWB1.tar) by Dev Ravindu Deshan works great too but Reboot to Recovery does not work properly all the time, so sometimes instead of Reboot to Recovery the changes happen when manually reboot to recovery using usb cable also sometimes it does not recognise pen drive. Till now I only managed to boot Tuki1.2 and the other Lineage 20 zip had Oplist error 1 issue. Hoping for GSI boot too later. Thanks for recovery
Click to expand...
Click to collapse
I'm not the dev btw, @naz664 is

Fredin_ said:
I'm not the dev btw, @naz664 is
Click to expand...
Click to collapse
Hi Friend,
Naz Roms great also
sidetalk: Do you know how to unlock CWD1 Stock Rom bootloader? my bootloader isnt unlocked fully? And in Shaomi phones which model would you recommend, it has fastboot so.

OldNoobOne said:
Hi Friend,
Naz Roms great also
sidetalk: Do you know how to unlock CWD1 Stock Rom bootloader? my bootloader isnt unlocked fully? And in Shaomi phones which model would you recommend, it has fastboot so.
Click to expand...
Click to collapse
What do you mean by it's not fully unlocked? iirc the toggle stays like that once the bootloader is unlocked.

Fredin_ said:
What do you mean by it's not fully unlocked? iirc the toggle stays like that once the bootloader is unlocked.
Click to expand...
Click to collapse
Hi Friend,
When I had unlocked the bootloader of the same device while it had A11 loaded in it, the oem unlock button was TOTALLY GREYED OUT (I swear I'm not lying), I mean even the toggle button was greyed out but in above picture you can see toggle buttons are Blue color and oem-unlock toggle button is light-blue but not fully greyed out, I didnt relock my bootloader before flashing A13 Stock CWD1 update
Now I cant flash GSI they refuse to boot always stuck on bootlogo.

OldNoobOne said:
Hi Friend,
When I had unlocked the bootloader of the same device while it had A11 loaded in it, the oem unlock button was TOTALLY GREYED OUT (I swear I'm not lying), I mean even the toggle button was greyed out but in above picture you can see toggle buttons are Blue color and oem-unlock toggle button is light-blue but not fully greyed out, I didnt relock my bootloader before flashing A13 Stock CWD1 update
Now I cant flash GSI they refuse to boot always stuck on bootlogo.
Click to expand...
Click to collapse
Don't think there is any in between state. If you can flash stuff, your bootloader is unlocked. If the GSI is not booting, that's some other issue. Try the new AOSP ROMs instead.
A51 Builds by Royna - Browse Files at SourceForge.net
sourceforge.net

Fredin_ said:
Don't think there is any in between state. If you can flash stuff, your bootloader is unlocked. If the GSI is not booting, that's some other issue. Try the new AOSP ROMs instead.
A51 Builds by Royna - Browse Files at SourceForge.net
sourceforge.net
Click to expand...
Click to collapse
Thanks Friend,
It looks like Royna's ROM zips (Lineage 20 & evolution_m21-ota-tq2b.230505.005.a1-06050648-community-unsigned.zip & crDroidAndroid-13.0-20230427-m21-v9.4.zip) not flashing, reason - TWRP error : 1 Assert failed : update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list") and repartition issue even while sideloading. The only one that boots is TukiRom1.2, I havent tried Tuki1.3 yet. I tried Roynas' TWRP files too but after boot to recovery they get stuck, the other TWRP files (TWRP-3.5.2-m21-v3.1-A12.tar & TWRP.3.7.0_11.-.M215FXXU3CWB1.tar) boot and work with some issues though.