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?

[Deprecated] [GUIDE] [NOOB-FRIENDLY] Custom ROM Flashing Guide

Custom ROM Flashing Guide​So after tons and tons of test builds, the good ol' devs managed to get everything working and gave us a super stable ROMs (many more to follow soon ). However, since our device supports A/B scheme, a newbie can find it rather difficult to get used to flashing ROMs, kernels and even GApps! So I decided to prepare a simple guide which should help you get used to flashing ROMs and lots of other stuff.
Disclaimer: If you don't know what bootloader is and/or don't know anything about Custom ROMs, I strongly recommend you to not try this on your own and rather watch some videos about them and the advantages/disadvantages associated with them.
Notes:
1. Prerequisites:
Unlocked Bootloader
ADB, Fastboot and Device Drivers (Google them)
Use Command Prompt instead of PowerShell for ease of use.
STEPS:
1. Boot into Fastboot mode (power+vol up) and run:
Code:
fastboot -w
Note your active slot from here. Mine is 'b' as can be seen from the pic attached. Yours can be 'a' or 'b'.
{
"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"
}
2. Download vbmeta from View attachment q_vbmeta.img and then do this:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
3. Now run the following command in your fastboot using pc(obviously):
If your active slot was 'a':
Code:
fastboot set_active b
If your active slot was 'b':
Code:
fastboot set_active a
4. Either restart bootloader directly from your phone (using volume and power keys) or do this:
Code:
fastboot reboot bootloader
Your fastboot screen should now look like the following. Notice the change in the active slot (if yours was 'a' in the previous step, it should be 'b' now).
5. It's TWRP time!!
Download TWRP (both boot.img and permanent zip) by @ThE_MarD from here.
Flash TWRP using:
Code:
fastboot flash boot boot.img
Make sure the name of your downloaded twrp image file is boot.img! If not, either rename the file or change the fastboot code to that filename.img
6. Now reboot to recovery using power and vol keys on your phone. You should see TWRP booting up now. If not, you've messed up somewhere, do the entire process again (correctly ).
7. Click on WIPE > ADVANCED WIPE, and choose System, Dalvik (Cache) and Data.
8. Check ROM notes and see if it comes with inbuilt vendor or not. If it does, you can skip this step. If it doesn't, ask for the required vendor from the maintainer.
Note: All A12 ROMs so far have come with inbuilt vendor.
9. Now, if you unlocked your bootloader via official apk (provided by Asus), then flash ABL.zip in TWRP/SHRP. However, if you unlocked unofficially, you can skip this step.
10. Time to flash the ROM of your choice. ! Click on INSTALL and then choose the ROM you want to flash. SWIPE>>>>>>>>>
11. Flash TWRP permanently using this: Permanent TWRP.
12. Flash the same vendor you flashed on the other slot. In other words, repeat Step 8 (no need to flash abl again) (skip flashing vendor if you skipped step 8).
Note (optional): Mount vendor before performing this step just to be safe.
13. Reboot to Recovery (IMPORTANT).
14. After rebooting, twrp would have automatically switched to your active slot (the one you had in Step 1)(check this in reboot section of twrp).
15. Now you can flash GApps, Magisk from the active slot anytime. This step varies from ROM to ROM as some ROMs have GApps pre-installed.
Note: Access TWRP by pressing power+vol down button simultaneously.
16. REBOOT>SYSTEM and you're done! Enjoy the ROM.
Credit Section:
1. Jackeagle -- TWRP and ROM Developer
2. Rohan Purohit -- ROM Developer
3. Sandeep.Sethi -- Kernel Developer
4. Marc Bourgoin -- TWRP and Device Developer
5. All the testers.
Thank you and I hope this guide benefits the community.

OSS Vendor Flashing Guide​Note: This guide is deprecated now, kindly refer to the guide above for latest ROM builds.
So after tons and tons of test builds, the good ol' devs managed to get everything working and gave us a super stable ROMs (many more to follow soon ). However, since our device supports A/B scheme, a newbie can find it rather difficult to get used to flashing ROMs, kernels and even GApps! So I decided to prepare a simple guide which should help you get used to flashing ROMs and lots of other stuff.
Disclaimer: If you don't know what bootloader is and/or don't know anything about Custom ROMs, I strongly recommend you to not try this on your own and rather watch some videos about them and the advantages/disadvantages associated with them.
Notes:
1. Prerequisites:
Unlocked Bootloader
ADB, Fastboot and Device Drivers (Google them)
Use Command Prompt instead of PowerShell for ease of use.
STEPS:
1. Boot into Fastboot mode (power+vol up) and run:
Code:
fastboot -w
Note your active slot from here. Mine is 'b' as can be seen from the pic attached. Yours can be 'a' or 'b'.
View attachment 4785824
2. Download vbmeta from View attachment 4961371 and then do this:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
3. Now run the following command in your fastboot using pc(obviously):
If your active slot was 'a':
Code:
fastboot set_active b
If your active slot was 'b':
Code:
fastboot set_active a
4. Either restart bootloader directly from your phone (using volume and power keys) or do this:
Code:
fastboot reboot bootloader
Your fastboot screen should now look like the following. Notice the change in the active slot (if yours was 'a' in the previous step, it should be 'b' now).
View attachment 4785825
5. It's TWRP time!!
Download TWRP (both boot.img and permanent zip) by Jackeagle from here.
Flash TWRP using:
Code:
fastboot flash boot boot.img
Make sure the name of your downloaded twrp image file is boot.img! If not, either rename the file or change the fastboot code to that filename.img
6. Now reboot to recovery using power and vol keys on your phone. You should see TWRP booting up now. If not, you've messed up somewhere, do the entire process again (correctly ).
7. Click on WIPE > ADVANCED WIPE, and choose System, Dalvik (Cache) and Data.
8. Flash OSS Vendor. You can flash via fastboot by downloading and extracting OSS_Fastboot.7z. Navigate cmd to OSS folder and run:
Code:
fastboot flash vendor vendor.img
Alternatively, you can simply flash OSS_Recovery.zip in TWRP/SHRP.
9. Now, if you unlocked your bootloader via official apk (provided by Asus), then flash ABL.zip in TWRP/SHRP. However, if you unlocked unofficially, you can skip this step.
10. Now, flash permanent twrp from here, change to the inactive slot and reboot to recovery again. Flash the same vendor you flashed on the other slot. In other words, repeat Step 8 (no need to flash abl again).
11. Time to flash the ROM of your choice. ! Click on INSTALL and then choose the ROM you want to flash. SWIPE>>>>>>>>>
12. Flash TWRP permanently using this: Permanent TWRP. Flash this simply in twrp.
Note (optional): Mount vendor before performing this step just to be safe.
13. Reboot to Recovery (IMPORTANT)
14. After rebooting, twrp would have automatically switched to your active slot (the one you had in Step 1)(check this in reboot section of twrp).
15. Now you can flash GApps, Magisk from the active slot anytime. This step varies from ROM to ROM as some ROMs have GApps pre-installed.
Note: Access TWRP by pressing power+vol down button simultaneously.
16. REBOOT>SYSTEM and you're done! Enjoy the ROM.
Credit Section:
1. Jackeagle -- TWRP and ROM Developer
2. Rohan Purohit -- ROM Developer
3. Sandeep.Sethi -- Kernel Developer
4. All the testers.
Thank you and I hope this guide benefits the community.

What is vbmeta zip doing?

If I'm on .58 flashing just vendor.img of .72 before all the steps helps?

bordi21 said:
What is vbmeta zip doing?
Click to expand...
Click to collapse
It disables the verified boot, so that you can flash gsi and custom roms. Without it, nothing other than zenui will boot.
jayd4321 said:
If I'm on .58 flashing just vendor.img of .72 before all the steps helps?
Click to expand...
Click to collapse
Yep flash vendor image and stock boot image of 72, and you'll be good to go!

I have performed step 8 and now I am in twrp. How to perform Step 9. Please suggest
Edit- Thanks did it by copying the files to my otg and flashing through twrp.

Thanks a lot for your comprehensive guide, got to unlock the bootloader and flash twrp as per the guide.
However, I have a problem booting the ROM; the ROM installs perfectly well and I can reboot into recovery but can't get past the "ASUS" screen upon actually trying to boot the ROM.
Am I missing something? I followed everything down precisely and I honestly don't know what am I messing up.
A little help would be appreciated.

viveknaudiyal said:
I have performed step 8 and now I am in twrp. How to perform Step 9. Please suggest
Edit- Thanks did it by copying the files to my otg and flashing through twrp.
Click to expand...
Click to collapse
Glad you were able to succeed
Xadus said:
Thanks a lot for your comprehensive guide, got to unlock the bootloader and flash twrp as per the guide.
However, I have a problem booting the ROM; the ROM installs perfectly well and I can reboot into recovery but can't get past the "ASUS" screen upon actually trying to boot the ROM.
Am I missing something? I followed everything down precisely and I honestly don't know what am I messing up.
A little help would be appreciated.
Click to expand...
Click to collapse
Okay! Can you provide your bootloader version and slots on which you have stock rom and twrp?

AryanAA said:
Glad you were able to succeed
Okay! Can you provide your bootloader version and slots on which you have stock rom and twrp?
Click to expand...
Click to collapse
my bootloader version was the latest one .72 and my stock ROM was on slot b, which I switched to a for flashing twrp and then booted into twrp and switched back to b to clear data, system and cache; flashed the ROM in the same slot and then flashed the permanent twrp as well.
Following all this i could reeboot back into twrp but couldn't get the ROM to boot.

Xadus said:
my bootloader version was the latest one .72 and my stock ROM was on slot b, which I switched to a for flashing twrp and then booted into twrp and switched back to b to clear data, system and cache; flashed the ROM in the same slot and then flashed the permanent twrp as well.
Following all this i could reeboot back into twrp but couldn't get the ROM to boot.
Click to expand...
Click to collapse
After wiping system,data,cache, you had to go back to slot A and then reboot to recovery and after that flash the rom (read point 10 of post).

@AryanAA can you please extend this guide on how to install magisk

AryanAA said:
After wiping system,data,cache, you had to go back to slot A and then reboot to recovery and after that flash the rom (read point 10 of post).
Click to expand...
Click to collapse
I tried that as well.
I must have repeated the process numerous times, i tired flashing it on the slot where my twrp is and i tired flashing it on the slot where was stock was as well in the next try; both incidences gave bootloop.

HELP
Encryption Unsuccessful!
Tried everything multiple times like mentioned in OP.

I was able to flash elementalX using this guide. Thanks for detailed info,i found this guide more understandable than the 1 we have in how to flash gsi thread.

milindmavadia said:
Encryption Unsuccessful!
Tried everything multiple times like mentioned in OP.
Click to expand...
Click to collapse
1. Flash DFE on both slots.
2. Go to fastboot and do fastboot -w on your rom slot

Xadus said:
I tried that as well.
I must have repeated the process numerous times, i tired flashing it on the slot where my twrp is and i tired flashing it on the slot where was stock was as well in the next try; both incidences gave bootloop.
Click to expand...
Click to collapse
Interesting. I think you should restart the whole process and flash rom only on inactive slot rather than both the slots!

viveknaudiyal said:
@AryanAA can you please extend this guide on how to install magisk
Click to expand...
Click to collapse
Process of flashing magisk is exactly same as gapps. Infact you can install gapps and magisk in one go.

AryanAA said:
Interesting. I think you should restart the whole process and flash rom only on inactive slot rather than both the slots!
Click to expand...
Click to collapse
Maybe i will give try in the future, for now i flashed the stock as i was frustrated by the whole thing.
Thanks a lot for your help though.

Fastboot -w ..it's says "waiting for device" can any one help?

Aruss5 said:
Fastboot -w ..it's says "waiting for device" can any one help?
Click to expand...
Click to collapse
You have to first install adb and fastboot drivers to your computer.

[ROM][SOFIAR][11][UNOFFICIAL][GAPPS][VANILLA] ArrowOS

{
"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"
}
ArrowOS​
ArrowOS is an AOSP/CAF based project started with the aim of keeping things simple, clean and neat.
Website: https://arrowos.net
Telegram: Channel | TG Portal/Links
Github: https://github.com/ArrowOS
Code Review: review.arrowos.net
E-mail: arrowos.contact
PayPal: Donate to us
Blog: blog.arrowos.net
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
You tell me
Be sure to include a log : via the Matlog app included or check how to
DOWNLOADS
Here!
INSTALLATION - TWRP
Unlocked Bootloader Required: google "unlock motorola bootloader"
Download the ArrowOS zip and copy to your external sd card
Download/Install firmware with the latest version of Moto Flash Tool
(this tool also prepares the b slot for custom rom installation)
Boot to the start/welcome screen
Power off and reboot to the bootloader/fastboot interface (power and volume down)
Install TWRP to slot a and slot b
Code:
fastboot flash recovery TWRP.img
fastboot flash recovery_b TWRP.img
Boot to TWRP (navigate with the volume buttons, select recovery, press power)
FORMAT DATA!!
Flash the ArrowOS zip
REBOOT TO RECOVERY!!
Reboot to system
Profit
INSTALLATION - FASTBOOTD
Unlocked Bootloader Required: google "unlock motorola bootloader"
Download the ArrowOS zip and extract it to your adb/fastboot folder
Download/Install firmware with the latest version of Moto Flash Tool
(this tool also prepares the b slot for custom rom installation)
Boot to the start/welcome screen
Power off and reboot to the bootloader/fastboot interface (power and volume down)
Install TWRP to slot a and slot b
Code:
fastboot flash recovery TWRP.img
fastboot flash recovery_b TWRP.img
Boot to TWRP (navigate with the volume buttons, select recovery, press power)
FORMAT DATA!!
In TWRP reboot menu, select fastboot, wait for it to reboot
Open a cmd window where you extracted the files to earlier and flash the ROM with the below commands
Code:
fastboot flash boot boot.img
fastboot flash vbmeta vbmeta.img
fastboot flash product product.img
fastboot flash system system.img
Reboot to system
Profit
*** Dont install Magisk until you have booted the ROM once
ROM Source: https://github.com/ArrowOS
Kernel Source: https://github.com/Odin1101/Project-Sofia/tree/Upstream-plus
Device Source: https://github.com/whatthef84/android_device_motorola_sofiar-1
Vendor Source: https://github.com/whatthef84/android_vendor_motorola_sofiar-1/tree/android-11
Many thanks to @vache for the above device/vendor trees, the flash tool, and building TWRP. The guy's a legend!

View attachment 5273685View attachment 5273649View attachment 5273651View attachment 5273653View attachment 5273655
View attachment 5273657View attachment 5273659View attachment 5273661View attachment 5273669View attachment 5273671View attachment 5273673View attachment 5273675View attachment 5273677View attachment 5273679

Agh, plain AOSP. I miss Havoc already.

Testing it out and everything thing seems smooth. I did find one minor issue for the people that like their temperatures in imperial units. You can change the lockscreen temp to imperial and it displays an F for farenheit but the temperature value is still Cecius.

Flashed twrp using minimal adb to recovery and recovery_b. Flashed arrow after formatting. Now I have no mobile data connection. Also getting: access point name settings are not available for this user, under apn. Tried fastboot erase modemst2, resetting, installing other roms doesn't work either. I'm on XT2041DL. Thoughts?

jonshmorg said:
Flashed twrp using minimal adb to recovery and recovery_b. Flashed arrow after formatting. Now I have no mobile data connection. Also getting: access point name settings are not available for this user, under apn. Tried fastboot erase modemst2, resetting, installing other roms doesn't work either. I'm on XT2041DL. Thoughts?
Click to expand...
Click to collapse
You will need to go back to rooted stock, and copy your apn_conf.xml file from product/etc to your sd card, amd replace it on arrow (or another rom)

Quantumstate said:
Agh, plain AOSP. I miss Havoc already.
Click to expand...
Click to collapse
Closest thing to havoc is crDroid ATM mate, it's on the forums here

This ROM is marked as only being compatible with sofiar, but I can confirm that everything seems to work on my sofia device.

Also, I had a problem when installing and I thought I should warn others. When I tried to install with TWRP, it failed and always booted back to TWRP when I tried to boot to system. When I tried the fastbootd method, it also failed because fastbootd is not available when TWRP is installed. Instead, I did this:
1. Skip the step of installing TWRP. It messes things up. You may be able to install it later, but I don't want to take my chances.
2. For the "format data" part in TWRP, run
Code:
fastboot -w
instead.
3. Instead of rebooting to fastboot from TWRP, run
Code:
fastboot reboot fastboot
.
4. Continue with the steps of installing boot, vbmeta, product, and system with fastboot.
Edit: It turns out I was using the wrong build of TWRP. Use the one linked in the original post, not the one elsewhere on the forums.

RaspberryPiBen said:
Also, I had a problem when installing and I thought I should warn others. When I tried to install with TWRP, it failed and always booted back to TWRP when I tried to boot to system. When I tried the fastbootd method, it also failed because fastbootd is not available when TWRP is installed. Instead, I did this:
1. Skip the step of installing TWRP. It messes things up. You may be able to install it later, but I don't want to take my chances.
2. For the "format data" part in TWRP, run
Code:
fastboot -w
instead.
3. Instead of rebooting to fastboot from TWRP, run
Code:
fastboot reboot fastboot
.
4. Continue with the steps of installing boot, vbmeta, product, and system with fastboot.
Click to expand...
Click to collapse
While in twrp, if you select reboot to fastboot, that is fastboot d

Beetle84 said:
While in twrp, if you select reboot to fastboot, that is fastboot d
Click to expand...
Click to collapse
I did not have an option for that. There was system, bootloader, "edl," recovery, slot A, and slot B, but no fastboot.

RaspberryPiBen said:
I did not have an option for that. There was system, bootloader, "edl," recovery, slot A, and slot B, but no fastboot.
Click to expand...
Click to collapse
Using the twrp linked here or another?

Beetle84 said:
Using the twrp linked here or another?
Click to expand...
Click to collapse
I just noticed that. I was using the TWRP build from https://forum.xda-developers.com/t/sofia-p-r-recovery-wip-twrp-3-4-0-0.4128353/ because I assumed that was what the link was for. Thank you.

Apps aren't able to see registered fingerprints. Fingerprint auth is grayed out and the apps complain "register fingerprints on the device settings".
I have tried:
Deleting and redoing fingerprints (just one and multiple) with and without rebooting.
Confirmed the fingerprints work for screen unlock and gestures.
Re-installed 08-04-21 Vanilla build with full format, issue persists.
Anything I missed to check? I do not have my phone rooted, so cannot see system logs using the logging app.
Using sofiar (moto g8 power). Tested the apps themselves on my second phone klte (Samsung S5 Lineageos 16) and fingerprints work just fine there.

Ok so I am so frustrated with this Moto G power , If anyone can please tell me what I am doing wrong...I have rooted and ran mutliple custome roms since back in the Jelly bean days but I have always been able to do all the fundamentals of owning root and making the most of my phone.. You guys have always been helpful . SO when i attempt flash a custom rom through adb folder ( because I think you cannot flash custom roms with twrp at all) attemtp to follow your instructions to the T
but every time after install of custom , and thats any custom rom i try to boot it up for first time , prior to re-twrping, adding gapps, or magisk rooting and it literally just stays on the new rom animation for hours until i give up and I have to rescue it with lenovo'S rescue tool . Any help would be awesome ?

jdude520 said:
Ok so I am so frustrated with this Moto G power , If anyone can please tell me what I am doing wrong...I have rooted and ran mutliple custome roms since back in the Jelly bean days but I have always been able to do all the fundamentals of owning root and making the most of my phone.. You guys have always been helpful . SO when i attempt flash a custom rom through adb folder ( because I think you cannot flash custom roms with twrp at all) attemtp to follow your instructions to the T
but every time after install of custom , and thats any custom rom i try to boot it up for first time , prior to re-twrping, adding gapps, or magisk rooting and it literally just stays on the new rom animation for hours until i give up and I have to rescue it with lenovo'S rescue tool . Any help would be awesome ?
Click to expand...
Click to collapse
You need to install the official android 10 rom to your phone using the moto flash tool linked in the first post. After that you can install custom roms from fastbootd with the first page instructions.
Android 11 official rom has some changed encryption stuff which I think is responsible for the infinite boot on custom roms when flashed over it. That's why you need to downgrade to android 10 first.

ok because I am on android 11 when it is back to stock flashed. I am using the lenovo tool and it is installing rpms31.q1.54-13-2_subsidy . So to clarify I need to roll back to android 10 to be able to flash any custom roms ? Or is there 11s that will work with a different method to flash them?

Carl-Robert said:
You need to install the official android 10 rom to your phone using the moto flash tool linked in the first post. After that you can install custom roms from fastbootd with the first page instructions.
Android 11 official rom has some changed encryption stuff which I think is responsible for the infinite boot on custom roms when flashed over it. That's why you need to downgrade to android 10 first.
Click to expand...
Click to collapse
I'm not the person with the problem, but thank you for the explanation. I installed my ROMs before Android 11 came out for this phone and I was planning to test the stock Android 11 ROM, so this information will be very useful.

jdude520 said:
ok because I am on android 11 when it is back to stock flashed. I am using the lenovo tool and it is installing rpms31.q1.54-13-2_subsidy . So to clarify I need to roll back to android 10 to be able to flash any custom roms ? Or is there 11s that will work with a different method to flash them?
Click to expand...
Click to collapse
I believe you have to roll back to Android 10. Custom Android 11 ROMs may work, but you can't install custom ROMs so that doesn't help.

actually it is rescuing me to android 11 no matter what i do

REALME C11 stuck in bootloop after flashing magisk.zip through TWRP recovery

I wanted to root my realme c11 rmx2185 so I unlocked the bootloader, flashed twrp recovery and then after flashing magisk.zip and selecting the reboot option it got stuck in boot loop. Now all I can do is to open the bootloader mode and nothing else otherwise it will keep rebooting again and again. If anyone can help me out I will be very grateful. Thank you.

Please answer the following questions
• What software version (e.g. RMX2185_11_A.87 etc.) were you using?
• Did you flash a magisk patched boot.img or a magisk installer?
• Did you do anything else before flashing Magisk and before the incident happened?
Please answer these so I can be able to help you.

• What software version (e.g. RMX2185_11_A.87 etc.) were you using?
RMX2185_11_A.93
• Did you flash a magisk patched boot.img or a magisk installer?
I downloaded magisk.zip and flashed it through TWRP custom recovery
• Did you do anything else before flashing Magisk and before the incident happened?
I unlocked the bootloader which cleared all the data on my phone ---> flashed TWRP.img
Before this incident my phone was absolutely in default condition.
When I asked this question my bootloader was unlocked but now I have locked it and all i can do is to press the power button to see the bootlooping. Can you help me out from here?
I locked the bootloader as my phone was in warranty so I thought it would be better to get it fixed by the company itself , but since my city has been locked down due to the covid situation, my phone is still with me unrepaired .
Now I can't even get to the bootloader mode by pressing buttons .
I wanted to root my device and I followed exactly what was given on this website > https://safeboxguide.com/how-to-root-realme-c11/

Sorry, wrong quote!

skund singh said:
I wanted to root my realme c11 rmx2185 so I unlocked the bootloader, flashed twrp recovery and then after flashing magisk.zip and selecting the reboot option it got stuck in boot loop. Now all I can do is to open the bootloader mode and nothing else otherwise it will keep rebooting again and again. If anyone can help me out I will be very grateful. Thank you.
Click to expand...
Click to collapse
1st, what do you mean by "open the bootloader mode" ? If what you mean is you can boot the device into fastboot mode ( using hard keys or else ) then the solution is quite easy. Just take the stock boot image of A93 ( if you don't have it then u can pm me, I'll send ) then flash into the device using follow commands :
- fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- fastboot flash boot boota93.img
- fastboot reboot
( remember to use patched vbmeta.img )
Your device will boot normal again.
2nd, from A87, the devs of Realmeme did something with the code so that if directly flashing magisk from custom recovery may random cause bootloop. So, my suggestion is to use fastboot command and flash the patched boot images like old times.

skund singh said:
• What software version (e.g. RMX2185_11_A.87 etc.) were you using?
RMX2185_11_A.93
• Did you flash a magisk patched boot.img or a magisk installer?
I downloaded magisk.zip and flashed it through TWRP custom recovery
• Did you do anything else before flashing Magisk and before the incident happened?
I unlocked the bootloader which cleared all the data on my phone ---> flashed TWRP.img
Before this incident my phone was absolutely in default condition.
When I asked this question my bootloader was unlocked but now I have locked it and all i can do is to press the power button to see the bootlooping. Can you help me out from here?
I locked the bootloader as my phone was in warranty so I thought it would be better to get it fixed by the company itself , but since my city has been locked down due to the covid situation, my phone is still with me unrepaired .
Now I can't even get to the bootloader mode by pressing buttons .
I wanted to root my device and I followed exactly what was given on this website > https://safeboxguide.com/how-to-root-realme-c11/
Click to expand...
Click to collapse
Now the situation is more complicated if your device's bootloader is locked. But why is that u r in boot looping and u choose to lock your bootloader????

LinhBT said:
1st, what do you mean by "open the bootloader mode" ? If what you mean is you can boot the device into fastboot mode ( using hard keys or else ) then the solution is quite easy. Just take the stock boot image of A93 ( if you don't have it then u can pm me, I'll send ) then flash into the device using follow commands :
- fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- fastboot flash boot boota93.img
- fastboot reboot
( remember to use patched vbmeta.img )
Your device will boot normal again.
2nd, from A87, the devs of Realmeme did something with the code so that if directly flashing magisk from custom recovery may random cause bootloop. So, my suggestion is to use fastboot command and flash the patched boot images like old times.
Click to expand...
Click to collapse
yes sir, by "open bootloader mode" I meant booting into fastboot mode.
Now I have realised the mistakes which I did previously--
1. I was not having the latest A93 stock boot image
2. I didn't disable the verification(- fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img)
I locked the bootloader again so that I can get it repaired for free as you know the warranty won't be valid if they found the bootloader unlocked.
Is there any other way this problem could be resolved???

skund singh said:
yes sir, by "open bootloader mode" I meant booting into fastboot mode.
Now I have realised the mistakes which I did previously--
1. I was not having the latest A93 stock boot image
2. I didn't disable the verification(- fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img)
I locked the bootloader again so that I can get it repaired for free as you know the warranty won't be valid if they found the bootloader unlocked.
Is there any other way this problem could be resolved???
Click to expand...
Click to collapse
Replied with file sent at your inbox.

Sorry for the late response.
Getting your phone back to life without the help of a Service Center will be tough.
Since you locked your bootloader, it’s gonna be quite hard to get you back. But when there’s a will there’s always a way.
If you have a laptop or a PC, you can use Platform Tools to reboot your phone to TWRP (since you mentioned that you already flashed TWRP). After booting to TWRP Recovery, you can simply flash a copy of a boot image. Since @LinhBT already sent you the file, you can use that one.
To install the boot image, go to Install, click Install Image, look for the boot image file, click on it, then choose Boot partition. Then flash.
After doing that, your phone should be back to normal. Tell me if it works for you.

I'm having almost the same problem, I want to root my phone to install TWRP and Install Lineage OS. I have also the update package RMX2185 A.95 in case I needed it. I patched the boot.img with magisk manager and locked the bootloader (fastboot flashing lock and fastboot flashing lock_critical).
Now my phone stuck in a Bootloop with a Red State Warning and I can't go to recovery mode.
Details:
Model: RMX2185
Firmware version: RMX2185 A.101
Rooted: No
{
"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"
}

Marielorteza said:
I'm having almost the same problem, I want to root my phone to install TWRP and Install Lineage OS. I have also the update package RMX2185 A.95 in case I needed it. I patched the boot.img with magisk manager and locked the bootloader (fastboot flashing lock and fastboot flashing lock_critical).
Now my phone stuck in a Bootloop with a Red State Warning and I can't go to recovery mode.
Details:
Model: RMX2185
Firmware version: RMX2185 A.101
Rooted: No
View attachment 5527747
Click to expand...
Click to collapse
I got my phone fixed at the service center . They replaced the motherboard as those people are not professionals they don't have enough knowledge about the softwares and stuff. I got it replaced as it was absolutely free for me( I locked the bootloader so that my warranty doesn't get void as i had mentioned earlier)
Getting the motherboard replaced was much easier for me than finding a pro on the internet who might have a solution for this.
I believe that there must be some solution to this problem other than getting the motherboard replaced.
If you find any solution please share.

My problem is I don't know where is my warranty card.

[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.