Related
Disclaimer
Code:
#include <std/disclaimer.h> /* * Your warranty is now void. * * 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 rooting your device * before doing 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. */
Downloads
Instructions
Unlock your bootloader if you haven't already. Detailed steps can be found here.
Download the ADB and fastboot tools, TWRP Recovery IMG file and Magisk zip from the link above.
Extract the ADB zip into a folder and copy the recovery file into the same folder as well.
Copy the Magisk zip file into your phone's internal storage.
Rename the recovery file to recovery.
In the ADB folder and click on the MFA32 to open a command prompt window.
Connect your phone to your PC and go to the Developer Options previously enabled. Find the USB Debugging option and enable it.
Now hold the Volume + Power Down buttons that will allow the phone to boot into Fastboot mode.
In the fastboot mode, type: fastboot devices.
If your device is detected, great. If not, check your connections, USB Debugging or see if proper device drivers are installed or not.
Next, type: fastboot flash recovery recovery.img. This will flash the recovery in a few seconds.
Next, type: fastboot reboot recovery. As a result, you are welcomed by the recovery screen.
Here, click on Install. Find the previously downloaded Magisk zip and select it to flash. This will flash the required binaries.
Reboot.
Open Play Store and install the Magisk Manager. This will allow you to take proper advantage of your root by using multiple modules with many features.
Enjoy!
Full Guide can be found here - http://xboard.in/redmi-6-pro-recovery-root/.
twrp recovery not reading internal storage.
Hi,
I have a Redmi 6 Pro Indian version with unlocked Boot-loader, MIUI Global 10.2 stable. Flashed twrp recovery (Sakura) successfully but booting into the recovery mode I find it cann't read internal memory (showing 0 MB) and I can't flash necessary files through it for rooting my device.
On rooting into twrp recovery mode, first asks for password for un-encription and when I provide device unlock password, after sometime, it shows password failed.
On tapping 'cancel' option, goes to home of twrp with no option to flash from internal storage since it is 0MB.
Fastboot getvar anti command shows nothing [ anti: (blank)]. Fastboot getvar all shows Rollback ver 2.
Please help.
@Aloke17 Your data are encrypted. You have to do format data. Notice that your internal memory will be erased. Make a backup before.
mar.ur said:
@Aloke17 Your data are encrypted. You have to do format data. Notice that your internal memory will be erased. Make a backup before.
Click to expand...
Click to collapse
It did not work. Have already done that with same result. Can you tell me if I can flash from external storage like otg pendrive etc.?
Aloke17 said:
It did not work. Have already done that with same result. Can you tell me if I can flash from external storage like otg pendrive etc.?
Click to expand...
Click to collapse
I think you did a wipe data, not format. Look at the picture below
mar.ur said:
I think you did a wipe data, not format. Look at the picture below
Click to expand...
Click to collapse
I know difference. Formatted data, not wiped. got same result.
Aloke17 said:
I know difference. Formatted data, not wiped. got same result.
Click to expand...
Click to collapse
Restart again to twrp after format
This is what I did (make sure the TWRP.img and lazy flasher zip (attached) are in the same directory as the adb folder):
1. Put phone to fastboot mode.
2. Run ADB command fastboot boot twrp.img (the twrp image downloaded). Phone will reboot into TWRP. It will ask for password to decrypt, just hit back and ignore it for now.
3. Go to Wipe, Format Data. Swipe to Factory Reset. Advanced Wipe: Dalvik/ ART Cache, Cache, System, Internal Storage.
4. Go to Mount and mount System.
5. Run ADB command adb push twrp.img /sdcard
6. Go to Install, Install Image, select the TWRP.img file that you just pushed and flash it as recovery but don't reboot yet.
7. Run ADB command adb push lazyflasher-no-verity-opt-encrypt.zip /sdcard
8. Go to Install, Install Zip, select the zip file that you just pushed.
9. Go to Reboot. Power Off.
10. Boot the Device into TWRP Recovery (press volume up + power button).
Hope this helps a noob like me who wasn't able to flash TWRP due to strange errors.
PS: Bootloader was unlocked and device was running MIUI 10.2.2 Stable (Chinese ROM). I switched to Revenge OS (from XDA) based on Android Pie after this.
Can anyone please tell me how to get rid of SAKURA anti rollback. I'm currently on miui rom global beta 9.6.27..????
I waana flash xiaomi.eu rom on my phone.
I bricked my phone while flashing EU rom direct through twrp.
I followed this guide and it worked. The good thing about this guide is you can mess up and then get the mobile back to working state. I copied from a blog but can not post the link as i have fewer than 10 posts.
The contents of the blog in case if its deleted
1. unlock bootloader.
1.1 To unlock bootloader linking your mobile number to the device is mandatory to unlock bootloader. Read my rant[1] at the end of this post during the flashing as it takes some time. For now move to step 2 after unlocking the bootloader
2. check if the bootloader is unlocked by running the command "fastboot oem device-info"
3. flash the system image.
3.1 Download the image from the mi.com site sakura_india_global_images_V10.3.2.0.PDMMIXM_20190527.0000.00_9.0_global_0aaaa35167.tgz # md5sum 0aaaa35167e8edd299f0dd9418f04c62
3.2 untar
3.3 cd sakura_india_global_images_V10.3.2.0.PDMMIXM_20190527.0000.00_9.0_global/
# poweroff mobile, press volume down + poweron to go to fastboot mode
3.4 ./flash_all.sh
4 twrp flashing using boot and not flash because flashing to recovery parition is successfull but the recovery boot does not launch twrp so use the temporary method(flashboot boot)
4.1 fastboot boot twrp-3.2.3-0-sakura.img # md5sum 16759dcc425042d6a63b635f777a7690
4.2 twrp -> advanced settings ->sideload -> check both the cache to wipe -> swipe
4.3 adb sideload Magisk-v19.4.zip # md5sum 2a1def27607601ecaa780ee4b15210c2
4.4 flashing lazyflasher went in to loading forever, so skip that. it works without lazy flashing
5. reboot will boot to system and then download the MagiskManager apk from its website
5.1 enable the developer options for adb to transfer the MagiskManager apk to mobile
5.2 adb push MagiskManager-v7.3.4.apk /sdcard # md5sum 16e9ad8767665234dea7896a4137288e
5.3 on the mobile install the apk
6. to test it
6.1 adb shell
6.2 su
6.3 the above command should pop up requesting for permissions for root.
[1] Rant on Xiaomi's lies on embracing developer culture
TLDR: Xiaomi don't lie about embracing the hacker ethic. Accept you are evil with some lame excuse that is much more respectable.
It is very evil of Xiaomi to make the user provide their mobile number(thats right, you must provide your **working** sim card number) to unlock the bootloader. They will not unlock if your sim is not active, you must enable internet on your sim, link the sim number to mi account and only then they will unlock the bootloader. If you just use wifi it is not supported and yet they lie on their faq that the need sim for data usage.
Here is the faq they do not say about the sim card requirement . I have archived it in case after reading this Xiaomi might change this faq
The Following is the Q&A of faq
> Isn't locking bootloader against Mi's 'geek' spirit?
> Locking bootloader is aimed to provide a better user experience, which we've been trying to do the whole time. In the meantime, we've provided an unlocking tool for senior users who know their ways around flashing and tweaking their devices.
> The unlocking procedure will need Internet access to get the unlocking password. Also, the Mi Account logged in on the Mi phone and the unlocking tool needs to be the same. Otherwise, the unlocking request will be denied. This will ensure that ill-intentioned people will not get access to your personal data.
Atleast the moto company wanted just the device id to unlock bootloader.
I was rooting for Xiaomi a long back when i saw their faq where the question was "Can i root my mi mobile " and the answer was something along the lines of "Of coures you can, what do you think of us . we embrace hacker ethic. Now i can not find a link to this faq. Is someone find this please comment the link, i will add here.
Hope this guide helps some one.
grv29a said:
Can anyone please tell me how to get rid of SAKURA anti rollback. I'm currently on miui rom global beta 9.6.27..????
I waana flash xiaomi.eu rom on my phone.
I bricked my phone while flashing EU rom direct through twrp.
Click to expand...
Click to collapse
Just try to unlock bootloader as i did.
After flashing, is there any 'unlock' under Mi Logo? If no, need to unlock again.
ROOT Vibe K5 Note LP or MM
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired.
* Please do some research if you have any concerns about features included in the products you find here 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.
* Your warranty will be void if you tamper with any part of your device/software.
* Same statement for XDA.
*/
Finally I got the method to root Lenovo Vibe K5 Note/A7020a48. If you are the one who is tired of searching how to root your device then you are at right place
But before we get started here are the things that you need (only for marshmallow user, lollipop user need only 1 thing which is given in method section)
Requirements
1. Your Device (of course)
2. Your Current Stock Rom's Firmware(You can easily get it in firmwarefile.com)
3. A Working PC (first check whether you can successfully connect your device to your pc or not)
4. ADB and Fastboot Tools
5. A working Brain
BONUS:-You can use this method to root any (5.1+) device (if it has general unlocking system, This method is supported by 95% devices).
Now It's Time To Rock
METHOD for Lollipop users
Download and install kingroot, open it and follow the tutorial given in that app
METHOD for Marshmallow Users
1. Make complete backup of your data, Everything except ext. storage of your device will be erased.
Now Follow the steps from 2 to 11 to unlock bootloader (you can skip it if you already unlocked it)
2. Go to your phone settings>About phone, tap on build no. 7 times and then go back you will see a new { } developer option just above the about phone option
3. Go to developer option and enable OEM unlocking and USB Debugging
4. Connect your device to your pc and install adb and fastboot tool system wide
5. Open command prompt or power shell
Note- Windows 10 users have to write .\ as prefix before every command.
6. Type
Code:
adb devices
You will see a prompt on device, just click on always allow this computer and press ok or allow whatever given there. You will see your a long set of random Numbers and letters after that if its written device then your phone is successfully connected to your pc.
7. After that type
Code:
adb reboot bootloader
Your phone will reboot into bootloader mode
8.Type
Code:
fastboot getvar all
There you see at last some lines which tells you about your bootloader status if you see Unlocked = no then your bootloader is locked and if it says Unlocked = yes then it is unlocked and if it is unlocked then you can stop here
Now for those who has a locked bootloader
9. Type
Code:
fastboot oem unlock
(In some devices which is shipped with android 6.0 or higher you may have to write fastboot flash unlock don't write this command for your Vibe K5 note/A7020a48)
10. Most Important step Type
Code:
fastboot format userdata
. If you skip this you may get bootloop (I skipped that and got bootloop)
11. Type again
Code:
fastboot getvar all
Now you will see Unlocked=yes and Congrats!!! you has unlocked your phone's bootloader
12. Disconnect your device and press and hold power button until it reboots
Now follow the steps to root your device
13. Now from your stock firmware file extract boot.img which is given in the folder named firmware and copy it any where in your device
14. Install magisk manager from here -> Official website
15. After opening the app you'll see it is written that Magisk not installed click on the install button and select patch boot.img option,
16. Now select your boot.img file which you have extracted from your firmware file. After selection it will start to patch that boot.img and store patched_boot.img file in download folder of your device internal storage, copy that file at any folder in your pc (not in desktop)
17. Now go to the folder where you copied that patched_boot.img file and press right click on your mouse while holding shift button of your keyboard (Shift + Right click in simple words) and you will see an additional option of open command window/powershell here click on that and connect your device with your pc.
18. Before getting started with commands follow step 2 and 3 again
19. Repeat step 6 and 7
20. After going into bootloader mode Type
Code:
fastboot flash boot patched_boot.img
(in this code boot is partition and patched_boot.img is file name which you are going to flash).
21. Disconnect your phone ,press and hold powerkey until it reboots
Congrats Device ROOTED!!!
#reserved
But there's a much simpler method to get root access with a single click. i cant able to attach photos.
did not work
Shubham1815 said:
#reserved
Click to expand...
Click to collapse
bro after entering the cmd fastboot oem unlock my lenovo vibe k5note displayed
fastboot mode
unlock not allowed
now what should i do ......plz help
Tried but not work for MM. The bootloader cannot be unlocked. Maybe your bootloader is different from the others, would you share it out?
mihir999 said:
bro after entering the cmd fastboot oem unlock my lenovo vibe k5note displayed
fastboot mode
unlock not allowed
now what should i do ......plz help
Click to expand...
Click to collapse
Do you enabled allow oem unlocking?
Shubham1815 said:
Do you enabled allow oem unlocking?
Click to expand...
Click to collapse
I enabled oem unlocking but still it shows "unlock not allowed"
Does this really works?? I want to try it
Did you actually unlock bootloader and root the device ? As far I know, in all other threads, none has confirmed any method.
After "fastboot getvar all" command, nothing happens. (PC => waiting for device.. PHONE => stuck at "Fastbood Mode"text)
Same for "fastboot oem unlock" command
I really want to permanent root for => LENOVO K5 NOTE (a7020a48). Years gone but no luck !
If your method is true then please answer us :crying:
Got stuck at "Unsupportive project for unlock" on my vibe K5note. Any help here please?
so . for those who are stuck at fast boot try and install the driver from this link :
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
this didn't work for me and i had to download and install "rescue and smart assistant" from the lenovo website
Rescue and Smart Assistant (RSA) - Lenovo Support AU
support.lenovo.com
once downloaded and installed , i could update the "Android" driver from device manager --> selecting the moto interface (not the composite one) instead the google one ( step by step : youtube.com/watch?v=nQjg6ePnGAc )
Once that's done , reboot to fastboot via adb
Now when I type fastboot devices I can finally see my device
however... i was getting " (bootloader) Unsupportive project for unlock "
no luck . . .
Edit:
if you however do have an OTG cable maybe try this method :
GitHub - BiltuDas1/unlock-Bootloader: Unlock Bootloader of any Device using PC or Android.
Unlock Bootloader of any Device using PC or Android. - GitHub - BiltuDas1/unlock-Bootloader: Unlock Bootloader of any Device using PC or Android.
github.com
good luck
any luck guys!?!?! or should i completey give up )
Hello guys, in this guide I will tell you how to unlock the bootloader of the Moto E6 Plus.
READ THE FULL GUIDE TO AVOID ERRORS IN THE PROCESS SINCE THIS UNLOCKING METHOD IS DIFFERENT FROM OTHER MOTOROLA PHONE.
DISCLAIMER:
Code:
/*
*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this system image 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.
*
*/
What we will do first is a downgrade to version 76 of firmware since the new versions it's not allowed unlock bootloader, for this we will use SP Flash Tool v5.1916 (since the most current version does not give an error) and later we will flash some files for complete the unlock bootloader besides that we will install TWRP to install some GSI since the stock system it cannot be used.
This process is for 32/2 and 64/4 variant.
Links of download at the end of the post.
WARNING: THIS PROCESS ERASES ALL USER DATA AND VOIDS THE WARRANTY IN ADDITION THAT THE SYSTEM STOCK CANNOT BE USED.
Spoiler: PROCESS OF THE UNLOCK WITH WINDOWS
Prerequisites:
A computer with Windows (bruh)
ADB and Fastboot installed
Have installed the device drivers to be detected in fastboot mode.
Have downloaded the lk, vbmeta and recovery files.
Have downloader SP Flashtool and the ROM to downgrade.
READ THE FULL GUIDE TO AVOID ERRORS IN THE PROCESS SINCE THIS UNLOCKING METHOD IS DIFFERENT FROM OTHER MOTOROLA PHONE.
Once the necessary files have been downloaded the process is the following"
Unpack the SP Flash Tool and open "flash_tool.exe" file.
Once opened the app they will have to press up to the right the section "Options" and select "Option", when i open them they have to uncheck the second option.
Then close the window and in the "Download-Agent" press in "Choose" and search inside the unzipped zip folder a file named "DA_SWSEC_1848_PTA29.76.bin" or similary and select it. Then in "Scatter-loading File" press in "Choose" and just like before navigate to the same rute and select the file "MT6765_Android_scatter" and click on "Ok", and in "Authentication File" some select "Choose" and select "auth_sv5.auth" file and click in "Ok".
Now remove the battery of the phone and in Flash Tool press on "Donwload" and connect the phone without battery and start to flash.
Once the flashing finishes place the battery again and boot it in FASTBOOT (not system), then in terminal put the next command to unlock the bootloader:
Code:
fastboot flashing unlock_critical
And press Volume + in the phone to unlock the bootlaoder and DO NOT reboot still
Spoiler: If you logged into the system directly
In case of having started in the system without installing the files, you will have to start in the recovery mode and do a factory format.
After that you can flash the files from fastboot.
Now flash the lk, vbmeta and twrp files with the next commands:
Code:
fastboot flash lk lk.img
fastboot flash vbmeta vbmeta.img
fastboot flash recovery twrp.img
Now restart in recovery and go to Wipe > System > Advanced options > Resize.
Without this it would appear that there is 8GB of memory instead of 32/64.Now it only remains to flash the GSI.
Spoiler: PROCESS OF THE UNLOCK WITH LINUX
Prerequisites:
A computer with Linux (bruh)
ADB and Fastboot installed
Have downloaded the lk, vbmeta and recovery files.
Have downloader SP Flashtool and the ROM to downgrade.
READ THE FULL GUIDE TO AVOID ERRORS IN THE PROCESS SINCE THIS UNLOCKING METHOD IS DIFFERENT FROM OTHER MOTOROLA PHONE.
Once the necessary files have been downloaded the process is the following
Unpack the SP Flash Tool, and mark as to executable "flash_tool" file and open as superuser, if you don't know the commands are the following:
Code:
sudo chmod +x flash_tool
sudo ./flash_tool
Now in the "Download-Agent" press in "Choose" and search inside the unzipped zip folder a file named "DA_SWSEC_1848_PTA29.76.bin" or similary and select it. Then in "Scatter-loading File" press in "Choose" and just like before navigate to the same rute and select the file "MT6765_Android_scatter" and click on "Ok", and in "Authentication File" some select "Choose" and select "auth_sv5.auth" file and click in "Ok".
Now remove the battery of the phone and in Flash Tool press on "Donwload" and connect the phone without battery and start to flash.
Once the flashing finishes place the battery again and boot it in FASTBOOT (not system), then in terminal put the next command to unlock the bootloader:
Code:
sudo fastboot flashing unlock_critical
And press Volume + in the phone to unlock bootloader and DO NOT reboot still.
Spoiler: If you logged into the system directly
In case of having started in the system without installing the files, you will have to start in the recovery mode and do a factory format.
After that you can flash the files from fastboot.
Now flash the lk, vbmeta and twrp files with the next commands:
Code:
sudo fastboot flash lk lk.img
sudo fastboot flash vbmeta vbmeta.img
sudo fastboot flash recovery twrp.img
Now restart in recovery and go to Wipe > System > Advanced options > Resize.
Without this it would appear that there is 8GB of memory instead of 32/64.Now it only remains to flash the GSI.
If you don't know which GSI to try first, I recommend one from Phhusson, Ermitain or Andy.
NOTE: The system will be encrypted, and in this build of TWRP the encryption is not support so the files of internal storage will appear with numbers and letters random, if you want to remove the encryption flash the dm-verity.
NOTE 2: After unlocking the bootloader you can update the firmware to the latest version, but you will have to flash the lk and vbmeta files again (besides of recovery).
NOTE 3: The GSI architectures for each variant are: A64 AB for 32/2 and ARM64 AB for 64/4.
NOTE 4: If you are going to flash a GSI with GApps you will first have to flash a vanilla Phhusson GSI and start in it, after that you have to flash the GSI with GApps WITHOUT wipes and you can use it normally
Links of download:
ROM to downgrade : https://mirrors.lolinet.com/firmware/moto/pokerp/official/RETLA/ (the one that says in the name 32B its for 32/2 variant and the one that says in the name 64B its for 64/4 variant, bruh)
SP Flashtool: https://spflashtool.com/download/ (download the 5.1916 version)
ADB and Fastboot (Windows only): https://androiddatahost.com/uq6us
lk, vbmeta and TWRP files: https://drive.google.com/drive/folders/19wDFLDOoFTIDO-sv3vxWJ-CUEG1Q3sl-?usp=sharing
Credits:
@eluallen to do the first guide of how to unlock the bootloader and vbmeta file.
@Siddk for the recovery.
@LichtEstarossx for lk file and give some development to pokerp ;-;.
Fastoh said:
Hello guys, in this guide I will tell you how to unlock the bootloader of the Moto E6 Plus
DISCLAIMER:
Code:
/*
*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this system image 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.
*
*/
What we will do first is a downgrade to version 76 of firmware since the new versions it's not allowed unlock bootloader, for this we will use SP Flash Tool v5.1916 (since the most current version does not give an error) and later we will flash some files for complete the unlock bootloader besides that we will install TWRP to install some GSI since the stock system it cannot be used.
This process is for 32/2 and 64/4 variant.
WARNING: THIS PROCESS ERASES ALL USER DATA AND VOIDS THE WARRANTY IN ADDITION THAT THE SYSTEM STOCK CANNOT BE USED.
Spoiler: PROCESS OF THE UNLOCK IN WINDOWS
Once the necessary files have been downloaded the process is the following"
Unpack the SP Flash Tool and open "flash_tool.exe" file.
Once opened the app they will have to press up to the right the section "Options" and select "Option", when i open them they have to uncheck the second option.
Then close the window and in the "Download-Agent" press in "Choose" and search inside the unzipped zip folder a file named "DA_SWSEC_1848_PTA29.76.bin" or similary and select it. Then in "Scatter-loading File" press in "Choose" and just like before navigate to the same rute and select the file "MT6765_Android_scatter" and click on "Ok", and in "Authentication File" some select "Choose" and select "auth_sv5.auth" file and click in "Ok".
Now remove the battery of the phone and in Flash Tool press on "Donwload" and connect the phone without battery and start to flash.
Once the flashing finishes place the battery again and boot it in FASTBOOT (not system), then in terminal put the next command to unlock the bootloader:
Code:
fastboot flashing unlock_critical
And press Volume + in the phone to unlock the bootlaoder and DO NOT reboot still
Now flash the lk, vbmeta and twrp files with the next commands:
Code:
fastboot flash lk lk.img
fastboot flash vbmeta vbmeta.img
fastboot flash recovery twrp.img
Now reboot to recovery and flash some GSI
If you don't know which try first with the GSI of Phhusson or Lineage of Andy
Spoiler: PROCESS OF THE UNLOCK IN LINUX
Once the necessary files have been downloaded the process is the following
Unpack the SP Flash Tool, and mark as to executable "flash_tool" file and open as superuser, if you don't know the commands are the following:
Code:
sudo chmod +x flash_tool
sudo ./flash_tool
Now in the "Download-Agent" press in "Choose" and search inside the unzipped zip folder a file named "DA_SWSEC_1848_PTA29.76.bin" or similary and select it. Then in "Scatter-loading File" press in "Choose" and just like before navigate to the same rute and select the file "MT6765_Android_scatter" and click on "Ok", and in "Authentication File" some select "Choose" and select "auth_sv5.auth" file and click in "Ok".
Now remove the battery of the phone and in Flash Tool press on "Donwload" and connect the phone without battery and start to flash.
Once the flashing finishes place the battery again and boot it in FASTBOOT (not system), then in terminal put the next command to unlock the bootloader:
Code:
sudo fastboot flashing unlock_critical
And press Volume + in the phone to unlock bootloader and DO NOT reboot still
Now flash the lk, vbmeta and twrp files with the next commands:
Code:
sudo fastboot flash lk lk.img
sudo fastboot flash vbmeta vbmeta.img
sudo fastboot flash recovery twrp.img
Now reboot to recovery and flash some GSI.
if you don't know which try first with the GSI of Phhusson or Lineage of Andy
NOTE: The system will be encrypted, if you want to remove the encryption flash the dm-verity.
NOTE 2: After unlocking the bootloader you can update the firmware to the latest version, but you will have to flash the lk and vbmeta files again (besides of recovery).
Links of download:
ROM to downgrade : https://mirrors.lolinet.com/firmware/moto/pokerp/official/RETLA/ (the one that says in the name 32B its for 32/2 variant and the one that says in the name 64B its for 64/4 variant, bruh)
SP Flashtool: https://spflashtool.com/download/ (download the 5.1924 version)
ADB for Windows: https://androiddatahost.com/uq6us
lk, vbmeta and TWRP files: https://drive.google.com/folderview?id=19wDFLDOoFTIDO-sv3vxWJ-CUEG1Q3sl-&usp=sharing
Click to expand...
Click to collapse
I've been looking for GSI-Treble support,
And my system drops this.
So in various posts people say "For this phone we have to install GSI aonly-Arm32"
I don't know what Is The Correct One And I Need Help
ShotRomsS6edge said:
I've been looking for GSI-Treble support,
And my system drops this.
So in various posts people say "For this phone we have to install GSI aonly-Arm32"
I don't know what Is The Correct One And I Need Help
Click to expand...
Click to collapse
Ahí te dice en la imagen, las GSIs compatibles son las que son A64 xd // There it tells you in the image, the compatible GSIs are those that are A64 xd
Dont get it, there is way too many fake websites with USB drivers for ADB and fastboot and none of them are working, ive tried your adb driver aswell but once I get into fastboot windows just says: Android device with a 28 error code which means that there is no driver installed, could you give me the link?
EDIT: adb only works when the device has booted.
simbanono said:
Dont get it, there is way too many fake websites with USB drivers for ADB and fastboot and none of them are working, ive tried your adb driver aswell but once I get into fastboot windows just says: Android device with a 28 error code which means that there is no driver installed, could you give me the link?
EDIT: adb only works when the device has booted.
Click to expand...
Click to collapse
What is missing are the drivers, try to download them from this link (is the link that came in the flash tool zip xd): https://androiddatahost.com/276a2
Fixed already ty
.
somebody know how to unlock bootloader moto e6 play xt2029-1? im trying to unlock bootloader and everthing i try it fails, please help me :c
cyanogenmodricky said:
somebody know how to unlock bootloader moto e6 play xt2029-1? im trying to unlock bootloader and everthing i try it fails, please help me :c
Click to expand...
Click to collapse
mmmmm, maybe downgrading to the oldest firmware version you can find
Fastoh said:
mmmmm, maybe downgrading to the oldest firmware version you can find
Click to expand...
Click to collapse
Well, that is what I have tried to do and spflashtools gives me many problems with this model :c
cyanogenmodricky said:
Well, that is what I have tried to do and spflashtools gives me many problems with this model :c
Click to expand...
Click to collapse
try the version of sp flashtool that uses LMSA
in the log it says which version
Fastoh said:
try the version of sp flashtool that uses LMSA
in the log it says which version
Click to expand...
Click to collapse
ohh ok, i will try it and i tell you if works :3
well i get make downgrade to the lowest version i found, now i can't unlock the bootloader with
fastboot flashing unlock_critical
it gives me "waiting device" :c
edit: i install adb, fastboot and moto drivers, now when i wirte fastboot flashing unlock appears "unknow command"
hey hi,i have a problem, so i did everything as you write it but when i did the flashtool thing it didn't recognize the phone, but it was making contact, i installed a lot of drivers until one of them make it work, so when i did the fastboot thing it wasn't recognize the phone again, what can i do? my phone is the 32/2 version
Alejandro2810 said:
hey hi,i have a problem, so i did everything as you write it but when i did the flashtool thing it didn't recognize the phone, but it was making contact, i installed a lot of drivers until one of them make it work, so when i did the fastboot thing it wasn't recognize the phone again, what can i do? my phone is the 32/2 version
Click to expand...
Click to collapse
what SO do you use? windows or linux? because in windows the fastboot mode did not work either ;-;
Fastoh said:
Now remove the battery of the phone and in Flash Tool press on "Donwload" and connect the phone without battery and start to flash.
Click to expand...
Click to collapse
But... How remove battery if this not removable?..
Mortyk said:
But... How remove battery if this not removable?..
Click to expand...
Click to collapse
what ._.? the moto e6 plus has a removable battery, I think you have the e6s instead of the e6 plus
Fastoh said:
what ._.? the moto e6 plus has a removable battery, I think you have the e6s instead of the e6 plus
Click to expand...
Click to collapse
Yeap i'm have e6s. I thought e6 plus have not removable battery also.
Do you know how to flash e6s?
Mortyk said:
Yeap i'm have e6s. I thought e6 plus have not removable battery also.
Do you know how to flash e6s?
Click to expand...
Click to collapse
mmmm, look first trying with lmsa to have as it tells you to do the firmware re-installation, then do the same steps you did in the LMSA but in the flashtool
If you want to downgrade you have to do it with the firmware of the e6s because if you do it with the e6 plus your phone will have birck.
This version of TWRP works on the Lenovo TB-X606FA, TB-X606F and TB-X606X.
Warning: this TWRP will not work for any of the Tab M10 variants with Qualcomm SOCs. For the TB-X505F, see this thread. For the TB-X605F/L, see this thread.
Code:
#include <std_disclaimer.h>
/*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Encryption
This device was released with Android 9 using full disk encryption (FDE). But we now have Android 13 GSIs for this tablet - and Android 13 does not support FDE. Android 13 only supports file-based encryption (FBE).
If you are using a ROM/GSI that uses FBE, you must use the twrp with -fbe in the name. If you use the wrong one, twrp will not be able to decrypt the data partition.
If you don't know if you're using FBE or FDE, then run this command while Android is running: adb shell getprop ro.crypto.type. If it returns "block", then your device is FDE. If it returns "file", it's FBE.
Installation
With a stock ROM, it is recommended that you also install Magisk. This will ensure TWRP remains your default recovery.
If Windows 10/11 does not recognise your tablet in fastboot mode, then see post #2.
Step-by-step guide
download TWRP to your PC (see the Download section below)
download the latest magisk.apk to your SDcard or OTG device. Change the filetype from "apk" to "zip".
get a copy of the vbmeta.img file from the stock ROM. It should be located in one of the subdirectories of LMSA's c:\ProgramData\LMSA\Download\RomFiles directory (after you download it using the LMSA rescue (power-off mode). This is only required the first time you flash TWRP, or the first time after you re-flash the whole stock ROM.
if your bootloader is already unlocked, go to step 5. To unlock bootloader:
on tablet: go to Settings->System->About and press "Build number" 7 times to enable Developer Options.
on tablet: go to Settings->System->DeveloperOptions. Turn on: "OEM unlocking" and "USB debugging".
connect tablet to your computer. Tablet will ask for permission to "Allow USB debugging". Tick "always allow" and select "OK".
backup any files you want to keep to an external device (MicroSD/OTG/computer), because the next step will wipe all your photos, files, google account etc on the tablet.
Now unlock the bootloader:
Code:
adb reboot bootloader
fastboot flashing unlock
follow the instructions on the tablet, then reboot to Android.
note: if fastboot reports <waiting for device>, then you need to install the Mediatek USB drivers. Go to developer.android.com/studio/run/oem-usb, then find the link to Mediatek (MTK) and follow the installation instructions.
note: after unlocking, tablet will take a while to come back up - because it has to do a factory reset and encrypt data again.
flash the TWRP image:
Code:
adb reboot bootloader
fastboot flash recovery twrp_X606FA_11.img
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot reboot recovery
backup the stock boot, system and vendor partitions in TWRP, if you don't have backups already
load Magisk:
In TWRP:
select "Install"
use "select storage" to locate device you stored magisk.zip on.
press the OK button
select the Magisk zip file
swipe to confirm Flash
when Magisk is finished, hit the "Reboot System" button
finished!
If you prefer to use button combos, rather than fastboot/ADB commands:
Vol Down + Power = fastboot mode
Vol Up + Vol Down + Power = recovery mode
Changelog
Code:
2023-03-27 - add TWRP 3.7.0 for FBE ROMs/GSIs (Android 13+) only
2022-02-06 - added separate download for TB-X606F
2021-12-16 - TWRP 3.6.0 updates
- support for Android 12 decryption (keymaster)
2021-07-05 - TWRP 3.5.2 updates
- corrected display of Cyrillic (and other non-ASCII characters) in file names on external drives (utf8)
2021-03-10 - TWRP 3.5.1 updates
- cherrypicked update 1995 to force splash screen to display on boot
- orientation is now landscape (for tablets)
- updated install instructions to reflect new Magisk apk (v22).
2021-02-02 - fix blank screen on boot - don't need to press power button anymore to wake screen up
2021-01-24 - TWRP 3.5.0_10-0: initial release
Downloads (FDE)
This will work with stock ROMs and most pre-A13 ROMs/GSIs.
TWRP 3.6.0_11-0 for X606FA: twrp-X606FA_11.img
TWRP 3.6.0_11-0 for X606F: twrp-X606F_11.img
Downloads (FBE)
This will not work with stock ROMs or most pre-A13 ROMs/GSIs. This is for ROMs/GSIs that use FBE to encrypt. Android 13+ only supports FBE.
TWRP 3.7.0_12-1 for X606FA with FBE encryption: twrp-X606F_12.1.fbe.img
Source code
https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp/tree/twrp-12.1
https://github.com/Yahoo-Mike/recovery_device_lenovo_X606FA/tree/android-12.1-fbe
Credits
The guys at TeamWin Recovery Project.
Everyone whose device trees I plagiarised from GitHub.
Contributors
Yahoo Mike
Created 2021-01-24
Last Updated 2023-03-27 (FBE support)
Windows 10/11 does not recognise tablet in fastboot mode
If your tablet is recognised by ADB but not by fastboot in Windows, you might need to get the latest versions of fastboot and the Mediatek usb drivers.
1. use the latest fastboot version
Make sure you are using the latest version of fastboot. There were major changes to fastboot for Android 10.
If you are using PowerShell, make sure it's picking up the fastboot you expect: fastboot --version. If not, use ./fastboot from the directory with the executable.
2. update device drivers
Try the latest Mediatek (MTK) drivers from Install OEM USB drivers. When they are loaded, they appear in Device Manager as "Kedacom USB Device/Android ADB Interface".
If Windows complains that the drivers are unsigned and refuses to load them, then do this as Administrator in Windows:
bcdedit /set testsigning on
reboot Windows
install the drivers
bcdedit /set testsigning off
In Windows 11, you might also need to turn off Secure Boot in your PC's BIOS to get the bcdedit command to work.
So I have the ZA5W0097US, would you suggest this wouldn't work?
ldeveraux said:
So I have the ZA5W0097US, would you suggest this wouldn't work?
Click to expand...
Click to collapse
That looks like a TB_X606F. This TWRP might work. We won't know for sure until someone tries.
Remember, the screen will be blank when TWRP boots up. You'll just have to click the power button twice to wake it up. I'll try and fix that over the next few days.
If you decide to try this TWRP and it doesn't work, please let me know what happens. And when you're booted into Android, can you tell me what the results of these ADB commands are?
Code:
adb shell getprop ro.hardware
adb shell getprop ro.boot.hardware
New version is now available in the first post.
The blank screen issue is mostly fixed...mostly. The screen is still blank on boot when decrypting data, but then it wakes up. No need to press the power button anymore.
I just got my TB-X606F (it's actually finishing setup right now) and I'm going to try flashing this TWRP onto it. I *think* the only difference between the "F" and "FA" version is that the "FA" comes with some sort of Alexa capability.
Both adb commands output "mt8768".
TB-X606F/ZA5T0300US (the manual also says TB-X606X) confirmed TWRP and Magisk are working. Had a hell of a time with getting fastboot to work on my main machine so I used a virtual machine to do everything with fastboot.
sirp0p0 said:
TB-X606F/ZA5T0300US (the manual also says TB-X606X) confirmed TWRP and Magisk are working. Had a hell of a time with getting fastboot to work on my main machine so I used a virtual machine to do everything with fastboot.
Click to expand...
Click to collapse
Cool. I'll update the OP.
Maybe check you have the latest version of fastboot on your main machine. There were some major changes for Android 10.
Good call. My adb and fastboot were both way out of date.
I also have the TB-X606F and was able to get this working 100%. I thought it was going to wipe my system so I backed everything up beforehand, but no wipe. Just replaced recovery with TWRP and here I am. Thanks a ton, great to have another TWRP recovery device!
ldeveraux said:
... I thought it was going to wipe my system so I backed everything up beforehand, but no wipe.
Click to expand...
Click to collapse
It will only wipe if you are unlocking the bootloader for the first time.
Thanks for the feedback.
Tried this process and ran into an issue. Flashed TWRP Okay, flash vbmeta ok, rebooted to twrp, but could not find magisk on sdcard for some reason. Not tablet won't take fastboot commands. Says waiting for device
adb device shows the tablet
snickle said:
Tried this process and ran into an issue. Flashed TWRP Okay, flash vbmeta ok, rebooted to twrp, but could not find magisk on sdcard for some reason. Not tablet won't take fastboot commands. Says waiting for device
adb device shows the tablet
Click to expand...
Click to collapse
Rebooteed to bootloader flashed twrp and vbmenta. REbooted to recovery and twrp came up. Installed magisk zip and rebooted. No root and stock recovery comes up instaead of TWRP.
THoughts?
Also still no fastboot commands available when tablet booted, just from bootloader.
Tried completely reflashing stock image, still no change.
snickle said:
...rebooted to twrp, but could not find magisk on sdcard for some reason.
Click to expand...
Click to collapse
You have to download Magisk-v21.4.zip and push it to /external_sd/.
If you did that, can you see your other files in /external_sd/ ?
snickle said:
...tablet won't take fastboot commands. Says waiting for device
adb device shows the tablet
Click to expand...
Click to collapse
Make sure you have the latest adb and fastboot from Google. There were some major changes to fastboot for Android 10.
Also make sure you have the latest USB drivers from Lenovo.
I have the latest adb and drivers. fastboot commands used to work.
I rebooted to bootloader and flashed thre patched boot image made with the canary version of magisk and got root.
I then reflashed twrp and vbmeta and things seem to be working. Except for fastboot commands whlle booted.
snickle said:
I have the latest adb and drivers. fastboot commands used to work.
Click to expand...
Click to collapse
For Windows, the latest fastboot --version is 31.0.0-7110759
snickle said:
...things seem to be working. Except for fastboot commands whlle booted.
Click to expand...
Click to collapse
If you are using Windows 10, check that the "Android Bootloader Interface" driver is loaded in Device Manager when the tablet is in fastboot mode. See this post.
And when you say "except for fastboot commands while booted", do you mean "while the tablet is booted in fastboot mode" or "while the tablet is booted in twrp recovery or Android system"?
Yahoo Mike said:
For Windows, the latest fastboot --version is 31.0.0-7110759
If you are using Windows 10, check that the "Android Bootloader Interface" driver is loaded in Device Manager when the tablet is in fastboot mode. See this post.
And when you say "except for fastboot commands while booted", do you mean "while the tablet is booted in fastboot mode" or "while the tablet is booted in twrp recovery or Android system"?
Click to expand...
Click to collapse
Latest ADB and drivers loaded.
Fastboot commands work while in fastboot mode, but do not work when booted to system any more.
snickle said:
Fastboot commands work while in fastboot mode, but do not work when booted to system any more.
Click to expand...
Click to collapse
That's ok. That's how it's supposed to work.
ADB only works when your device is in recovery or system. It won't work when you're in fastboot or EDL mode.
Fastboot only works when your device is in fastboot mode. It won't work when you're in EDL, recovery or system.
The fastboot utility is an interface to the Android bootloader. When your device is in fastboot mode, you can use this utility to configure (some of) the bootloader and partition images. That's about it. I'm oversimplifying again, but...once the bootloader has passed on execution to EDL or a kernel (recovery or system), the fastboot utility can't work because the bootloader process is no longer running.
Unhelpfully fastboot just displays the "waiting for device" message, rather than something like "waiting for device to enter fastboot mode".
I hope that helps explain what's going on.
Twrp is working as expected no issues I have found, except for the need to press the power button s few times after booting into recovery to get twrp screen.
Hello! I need a bit of help... I have a TB-606F, 4GB/64GB version
I'm stuck on step 5. I've unlocked the bootloader, flashing TWRP and vbmeta seems successful, but then I cannot reboot into recovery. Using the fastboot reboot command I get "fastboot: usage: unknown reboot target recovery". If I try to reboot using volume up + volume down + power it eventually boots to Android.
Any thoughts are much appreciated!
thanks to yahoo mike for solving the problem with the TWRP not working, you're a saint!
due to the fact that i want to prevent the painful process of trying to find out which twrp works for TB-X605L_S210224_200910_ROW, i will have to point it out to those who have the kind of firmware installed on their Lenovo Tab M10 and try to use TWRP version higher than 4.0 and it doesnt work - TWRP will never work, but there's still a way out for people who want root:
THE MAGISK BOOT.IMG METHOD IN THE FLESH FOR PEOPLE WHOSE TABLETS CANT GET ROOTED THE TWRP WAY!
Disclaimer: the boot.img file which was patched by magisk only works with TB-X605L_S210224_200910_ROW
For other versions you have to use LMSA to snatch the firmware and get the specific files.
This method also works on TB-X605X - same LMSA procedure, same result.
what will you need:
the first and important one - knowledge that i dont care if you couldnt use your 2 brain cells to follow the steps and proceed to brick the device by slapping a boot image on a recovery one and the fact that if you havent started the process yet your data (if theyre not backed up) will be WIPED
Click to expand...
Click to collapse
2 - a tablet, obviously (common sense)
3 - a computer
4 - Android SDK platform tools
5 - boot.img with magisk installed on it
6 (optional) - If you have no ramdisk, LMSA to at least get the recovery.img file
THE STEPS:
if you havent started the rooting process yet:
Spoiler
Code:
1 - Go to device details and tap the serial number 7 times, dev mode should activate
2 - Go to dev settings and activate OEM unlocking and USB debugging
3 - On your computer you should have downloaded SDK platform tools, extract in C:/
4 - Afterwards get into the platform-tools folder, click the path line and type CMD
5 - Type adb devices to see if it installed correctly, your device should appear
6 - Type adb reboot bootloader, wait until the device reboots, you should see FASTBOOT MODE in red text
7 (LAST CHANCE TO BACK UP YOUR FILES, IF YOU PROCEED YOUR UNBACKED DATA WILL BE PERMANENTLY WIPED) - Type this: fastboot oem unlock-go
8 - type fastboot reboot
YOU MAY PROCEED TO THE ROOTING PROCESS PART 2.
If you already unlocked OEM (ROOTING PROCESS PART 2):
1 - Go on your device and download Magisk Manager (Version is 23.0)
2 - install the APK file
3 - open magisk manager and check the ramdisk
We will look at 2 situations:
Yay! Ramdisk is checked as Yes! The process will be hassle free and you wont have to use LMSA to get the firmware!:
Spoiler
Code:
1 - On your computer put the modified boot.img file into the platform-tools folder (Dont worry, it doesnt bite)
2 - Move on to the CMD prompt and enter: adb reboot bootloader
3 - then type in: fastboot flash boot (THE FILE)
4 - after that reboot your device by typing in: fastboot reboot
5 - HURRAH! Now you have installed root using the boot method AND without TWRP! Its best to check it with root checker for best measure though.
OH HELL NAH! IN THIS RARE CIRCUMSTANCE YOUR RAMDISK IS LITERALLY NONEXISTANT AS CONFIRMED BY THE CHECKED NO! HERE'S THE HARD WAY:
Spoiler
Code:
1 - If not already, download LMSA (or just search on the internet lul)
2 - Install LMSA and make sure you have connected your device to the computer
3 - Go to the Rescue tab and download the Firmware
4 - the path should be C:\ProgramData\LMSA\Download\RomFiles\TB-X605L_S210224_200910_ROW, you should see recovery.img
5 - snatch it and then place it into the download folder of your device
6 - use magisk manager to install magisk on the recovery image (MAKE SURE TO CHECK RECOVERY MODE IN MAGISK MANAGER OPTIONS, IT MUST BE CHECKED!!!!)
7 - snatch it by typing the command into the command prompt: adb pull /sdcard/Download/magisk_patched_[random_strings].img
8 - boot your device into bootloader with this: adb reboot bootloader
9 - now flash it into recovery: fastboot flash recovery magisk_patched_[random strings].img
10 - reboot with fastboot reboot
11 - Congrats, you got root! Unfortunately for you and your nonexistant ramdisk you have to boot into recovery to run the system with magisk
12 - use the recovery key combo until you see the splash screen, then release the keys. You will boot into magisk as it hijacks the recovery
13 - and thats how you root without ramdisk! you have gone through the entire pain of having to now use the recovery combo and releasing keys in order to boot into the system with root, but hey, you got root!
if you brick your device and/or meet the device reaper under the name of QUALCOMM USB DIAGNOSTIC, you're pretty much dead and i do not take any responsibility. that was your choice to go with this method.
if you blame me for anything ranging from alarm clock app failing and cant wake you up because it couldnt access the vibration and/or sound to a god forsaken thermonuclear war because the error code of the qualcomm usb diagnostic somehow gave you nuclear access codes, here's the response: COPE AND SEETHE
Click to expand...
Click to collapse