Database Users

TWRP 2.7.1.0 fails to flash xt907 roms

I'm using TWRP 2.7.1.0 on a Droid Razr M Kitkat. Whenever I try to flash an xt907 rom it gives me the error:
This package is for xt925,xt926, ..... and on, and doesn't flash. Here's how I've done the process:
Revert to stock KitKat with the VZW and RSD Lite tool
Install towel root and root my phone
Install motopacalypse and unlocked my phone (it's already unlocked so I've ran that once just to unlock it)
Reboot into fastboot and flash TWRP for Razr M
Then reboot to recovery and try to flash an xt907 rom
I've tried B62-Comotion, I've tried an AOKP PURE rom and various others, but it gives me that same error everytime.
Any help on what to do?

I believe the Roms your trying to flash has asserts in the updater-script and is built for the xt925/926 where are you getting the Roms from? Are you sure that they are compatible with the M xt907…? As the asserts in the updater-script are to prevent people from flashing the ROM on a device its not meant for so you won't brick your device...
Sent from my XT907 using XDA Premium 4 mobile app

Like EZKnives said, it looks like you're trying to flash ROMs that aren't compatible.
Sent from your Mom's M8

yes, make sure it is specifically for the xt907 or is a compatible msm8960 build on the KB bootloader.

[Q] What I'm doing wrong??
Following my previous question and remembering the great performance of MIUIandroid V4 for GT-i5500, I want to install MIUIv5 4.2.7 ROM for our Smartphone... Because I'm coming from Samsung GT-i5500 and the only thing we need to use is ODIN, I'm searching how to flash ANY rom on our device and I didn't find any information/tutorial/guide/how-to; only the CM guide, what is very awful.
I've finally reached to unlock the bootloader and I verified what I have "UNLOCKED Code 3" FastBoot. I'm in the point where I need to install an recovery.
After almost 30 minutes searching, I found the tool "Flashify". I've the CWM-Based Recovery img on my device and I want to install it (I really don't understand the instructions what CyanogenMod gave me).
Flash > Recovery image > Choose a file > recovery.clo...-xt907.img (I'm reading from the device).
It ask me if I want to flash the recovery. Answer: Yup!
After reboot: The image "Warning Bootloader Unlocked", and... ... ... ... nothing. Just nothing. It lasts A LOT for come out of this screen (that only happened when I installed the Recovery), reboots without any order, shows again that ugly screen and turns on the OS. When I turn off and hold Vol Down + Power buttons, NOTHING.
Can I know what I'm doing wrong??

What's your system version...? Sounds like you flashed the incorrect recovery
We cannot teach people anything; we can only help them discover it within themselves.

ezknives said:
What's your system version...? Sounds like you flashed the incorrect recovery
We cannot teach people anything; we can only help them discover it within themselves.
Click to expand...
Click to collapse
If you're talking with me:
{
"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"
}
I hope this helps. Also, I'm downloading the Recovery what is at the page of rommanager. Flashify didn't found ANY recovery for my smartphone
The name of the recovery (I think) explains for itself:
recovery-clockwork-6.0.4.4-xt907.img
Click to expand...
Click to collapse
EDIT:
A think what happened recently: When I'm in the OS, the device didn't recognize the commands. meanwhile it says "attatched", when I send any command it says <waiting for device>.
When I reload the fastboot via Power Menu, it recognizes ALL the commands. How I know? I changed the ugly Unlocked BootLoader image with the original M in a red circle

Pedreo1997 said:
If you're talking with me:
I hope this helps. Also, I'm downloading the Recovery what is at the page of rommanager. Flashify didn't found ANY recovery for my smartphone
The name of the recovery (I think) explains for itself:
EDIT:
A think what happened recently: When I'm in the OS, the device didn't recognize the commands. meanwhile it says "attatched", when I send any command it says <waiting for device>.
When I reload the fastboot via Power Menu, it recognizes ALL the commands. How I know? I changed the ugly Unlocked BootLoader image with the original M in a red circle
Click to expand...
Click to collapse
OK... I can't see that image bit the name looks right here are the recoveries... And here are some boot logos..
We cannot teach people anything; we can only help them discover it within themselves.

ezknives said:
OK... I can't see that image bit the name looks right here are the recoveries... And here are some boot logos..
We cannot teach people anything; we can only help them discover it within themselves.
Click to expand...
Click to collapse
I'm curious about why you can't see the image. I was hoping, instead, what you were going to confront me about the fact what it's in spanish (I know it's obvious what I'm not from an English-talking country)... If you want, here is the text what is in the image:
System Version: 183.46.10.XT907.Verizon.en.US
Model number: DROID RAZR M
Android version: 4.4.2
Baseband version: SM_BP_101031.042.32.86P
Kernel Version:
3.4.42-g5170b6b
[email protected] #1
Fri May 2 00:30:06 PDT 2014
Comp. number: KDA20.62-10.1
Comp. Date: Fri May 2 00:20:25 PDT 2014
Click to expand...
Click to collapse
And about the boot logo, it was only an extra I was telling: The fastboot is working because I reached to edit the ugly Warning Image, that's it
For end: Are you telling what for our device the recovery what is in the official page of CyanogenMod isn't the right one? However, I'm going to try with the first link. Thanks

@pedreo... That's what I was checking for... I don't use CWM but the one for the M on 4.4.2 is CWM6049-RAZR-HD_M-KITKAT.img which is in the link previously post... I hear a lot of people have issues with CWM... TWRP seems to work best.... Its just best to pull it from the posted link to ensure you have the proper version... RikRong knows more about it(well pretty much everything android) then me ..
We cannot teach people anything; we can only help them discover it within themselves.

Pedreo1997 said:
I'm curious about why you can't see the image. I was hoping, instead, what you were going to confront me about the fact what it's in spanish (I know it's obvious what I'm not from an English-talking country)... If you want, here is the text what is in the image:
And about the boot logo, it was only an extra I was telling: The fastboot is working because I reached to edit the ugly Warning Image, that's it
For end: Are you telling what for our device the recovery what is in the official page of CyanogenMod isn't the right one? However, I'm going to try with the first link. Thanks
Click to expand...
Click to collapse
Yeah, neither CWM or TWRP are official for this phone, so they won't show up on the team's websites. The link that EzKnives posted has the recoveries you want.
Sent from your Mom's M8

Philz Recovery
If you are intent on using a CWM type of recovery for our Razr M, the current version of philz recovery is working on our devices, thanks to the unified moto_msm8960.
Here is the link:
https: //goo.im/devs/philz_touch/CWM_Advanced_Edition/moto_msm8960/
Being that I haven't posted before on the site, (been lurking for years), I am not able to post the link as clickable, so copy and paste and remove spaces. Please keep in mind that this will only work on the KK Bootloader, but in my tests, it works just fine. I do prefer the TWRP 2.7.1.0 overall, but philz is not bad.
Hope this helps.

[GUIDE] How to flash the COS 13 update. Even if you get the release keys error

Alright.
I had this problem for a while and I figured out how to flash the update without the need to factory reset or change the update script of the update file.
Even if you get the user/release-keys error message. EXAMPLE:
{
"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"
}
You have to be using the latest lollipop release before updating. That means you have to be on YOG7DAS2K1 before attempting.
This worked out for me. But it might not work for you. I do not believe it can destroy your phone and switch some satellites off, but still, not responsible if it did so.
Requirments:
You have to have TWRP now or you at least have ROOT and any flashing app like flashify.
Download COS 13 update file. here https://www.androidfilehost.com/?fid=24459283995316311
Download the latest CyanogenMod Recovery https://download.cyanogenmod.org/?device=bacon
Download the cm-12.1-YOG7DAS2K1 full ROM [url]https://www.androidfilehost.com/?fid=24369303960686198[/URL]
Guide:
Make sure the update cyanogen recovery option is checked in developer options.
Flash CyanogenMod Recovery downloaded before.
Reboot into it.
Use the update function in CyanogenMod Recovery and choose cm-12.1-YOG7DAS2K1 as the update file. It might take a while.
Now reboot to your phone. When booted and running, reboot to recovery.
Now you are running COS recovery. Update with the incremental.
That is it.
I hope this works out for you.
EXTRA: How to ROOT and have TWRP as a recovery:
Requirements:
A laptop.
Download TWRP and adb drivers on the laptop and the SuperSU and TWRP on your phone
Download Oneplus One TWRP Recovery [url]https://dl.twrp.me/bacon/twrp-3.0.2-0-bacon.img.html[/URL]
Get any adb divers. This one suffice [url]http://forum.xda-developers.com/google-nexus-5/development/adb-fb-apx-driver-universal-naked-t2513339[/URL]
Download the latest SuperSu [url]https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip[/URL]
Guide:
Reboot into bootloader: you can do this in many ways. A simple google search will show you how. Easiest way is to turn the phone off and hold the volume up and power long enough for the phone to boot into bootloader.
Connect your phone to your laptop
Run the adb: I assume you are using windows of course. First put the TWRP .img file in this folder. Hold shift and right click in the folder downloaded above. A 'Open command window here' option will be there. Click it and write in the window
Code:
fastboot boot twrp-3.0.2-0-bacon.img
. A hint: you can just write twrp and hit TAB, it will complete the filename. Or you can rename the downloaded file to just twrp.img
Check your phone, you will be running TWRP temporarily. You now have the option to ROOT only by flashing the SuperSU file downloaded on your phone. If you reboot now you will lose TWRP and get back to the official COS Recovery. If you want TWRP for good flash the TWRP file downloaded on your phone before.
I hope this is easy. It actually is. just follow it step by step.

If you could provide us the guide to root and come back to twrp I would be extremely happy

bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
fastboot flash latest twrp and flash SuperSU BETA
THANK the post if I deserve

bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
if you need a guide to root, this means you are not rooted, and if you are not rooted most probably you already have stock recovery, which means you can just install the OTA update without any issues.

bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
Added as requested. I hope you find it easy.

y2kkingboy said:
Added as requested. I hope you find it easy.
Click to expand...
Click to collapse
Thank you, you made my life easier, but when I tried to run the twrp through fastboot I got an error and I got the solution writing "fastboot boot twrp.img" (after renaming the file).

bisio971 said:
Thank you, you made my life easier, but when I tried to run the twrp through fastboot I got an error and I got the solution writing "fastboot boot twrp.img" (after renaming the file).
Click to expand...
Click to collapse
Yeah. I mad a mistake there. Thank you and glad it helped.

If I do this what happens to my data?? I'm on cm 12. 1.1, rooted & running twrp.
---------- Post added at 12:20 AM ---------- Previous post was at 12:18 AM ----------
Link for cos13 that works with this method?

thinleytsering9 said:
If I do this what happens to my data?? I'm on cm 12. 1.1, rooted & running twrp.
---------- Post added at 12:20 AM ---------- Previous post was at 12:18 AM ----------
Link for cos13 that works with this method?
Click to expand...
Click to collapse
As I stated before you have to be on COS 12.1 YOG7DAS2K1. This method should not format your phone or remove any data as there is no factory reset step.
As for the link they are all over the place now. I used the official one. I'll link it for your convenience.

can anyone please pull the stock recovery from COS 13, not 12. I kinda screwed up while updating and now stuck in bootloop.
Update: The issue is resolved. The issue was because of SuperSu 2.46. Installing the latest TWRP and SuperSu 2.66 fixed it. Marshmallow is now rooted!

Thank you very much! After going back to stock and still not receiving the update for more than a week (well at least it felt like a week, Lol) I decided to flash a full COS 13 zip floating around. Instantly liked the new ROM but it had root/symlink issues only to be resolved when flashing a custom kernel it seems. Not what I really wanted so then I stumbled onto your thread and this technique worked 100%! I was on DAS2K1 (flashed thru a custom recovery) already and had several failed attempts flashing just the incremental outright (thru stock recovery)., but by flashing DAS2K1 thru stock recovery first as you suggest then the incremental seems to do the trick.

I did it all the steps, but my phone doesn't not start. After optimizing aplications I have bootloop at "cyanogen modready".
L.E. I think the problem was one of old aplications. After a clean install everything works.

This is the best thing Oneplus one i ever experience.COS13 give my Oneplus one a new breathe of life .This update better than crap lolipop.No Bug for me until now,only google play service need to update twice in play store,its auto reboot itself twice and wholla,super speed UX.The best thing i ever have.I apply update from CM-12-0-YNG1TAS17L Build LRX22G using this method and it works flawlessly
I don't need to factory reset or wipe cache .
I flash full stock ROM cm-12.1-YOG7DAS2K1 and apply update through CyanogenMod Recovery only and nothing else.
Now my oneplus one is rooted and TWRP install using ADB and its fly.All rooted apps is working together with Adaway.
Thanks Cyanogen team for make this 2 years old flagship killer a beast .
Only thing not satisfied is gone signal and wifi status (connectivity indicator ).I need to swipe down to see my transfer data working (what a bummer ).
Thanks so much for this magical guide (y2kkingboy) Yours truly Oneplus one diehard fan.

I was already on cm-12.1-YOG7DAS2K1, however rooted. So even if I had been offered the OTA it would have failed.
Your guide got me updated, first time with no problems.
6.0.1 is such an improvement on 5.1.1, I tried a couple of other 6.0 roms, however this has by far been the most stable and bug free.
Cheers for the tutorial!

u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file

#sychrome# said:
u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file
Click to expand...
Click to collapse
Can you provide more info? i've always had trouble updating when rooted.

InsaneNutter said:
Can you provide more info? i've always had trouble updating when rooted.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2522762

u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file
Click to expand...
Click to collapse
Can you provide more info? i've always had trouble updating when rooted.
Click to expand...
Click to collapse
I had tried this before and it did not work for me. Kept getting an error saying "the signature file was not a complete file" and therefore it didn't flash. But it may have been editing error on my part. This method works just fine and no need to give up your data either.

Having tried many other ways, I got it done with this instruction.
Thank you!

marxu said:
Having tried many other ways, I got it done with this instruction.
Thank you!
Click to expand...
Click to collapse
Glad I helped.

[Recoveries]TWRP Recovery For Meizu M2 Mini

{
"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"
}
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom "ROM" like OmniROM
Requirements
Root+Bootloader Unlocked
Flashing Instructions
After Unlocking Bootloader (If you dont know how to do it then go here)
[url]https://forum.xda-developers.com/meizu-m2-mini/how-to/guide-unlock-bootloaderinstall-twrp-t3390799[/URL]
Enter In fastboot.Then type.
"fastboot flash recovery recovery.img"
wait a minute turn off the phone. and enter recovery (Power + vol up until vibration)you'll Be in TWRP
Download Links
Old Recovery Version 2.8
[url]https://drive.google.com/open?id=0Bz6Fq2POoJTlMXd3YzJhTnUxeVU[/URL]
Mid Recovery 3.10 Latest
[url]https://drive.google.com/open?id=0Bz6Fq2POoJTlYnpCaXhSOUxjX0E[/URL]
New Recovery 3.1.1
[url]https://drive.google.com/file/d/0Bz6Fq2POoJTlRjh4ZkppWUJ4Qm8/view?usp=drivesdk[/URL]
Latest Recovery 3.2.1
[url]https://drive.google.com/file/d/1ftYtD2Tm0MdKBv_ZtVQHGJEcCuflb6Oe/view?usp=drivesdk[/URL]
Don't Forget To Press Thanks if you like it :good: :good:
Regards~
Murtaza Piplod

what's news bro?

ADIB27 said:
what's news bro?
Click to expand...
Click to collapse
updated with latest features of the latest recovery released by TWRP read changelogs at there TWRP site

heelo there,
my meizu m2 now keep rebooting and enter the twrp recovery.
even i hold the power button, it still cannot totally shutdown the phone.
any solution?
please help me.

maxisgsm said:
heelo there,
my meizu m2 now keep rebooting and enter the twrp recovery.
even i hold the power button, it still cannot totally shutdown the phone.
any solution?
please help me.
Click to expand...
Click to collapse
Try clear dalvik and cache.

adarshm4you said:
Try clear dalvik and cache.
Click to expand...
Click to collapse
the problem is after the phone reboot, it enter twrp menu, dan go to format menu then reboot again ......

maxisgsm said:
the problem is after the phone reboot, it enter twrp menu, dan go to format menu then reboot again ......
Click to expand...
Click to collapse
I think there will be some mess in installed os reflash it after taking a backup.

adarshm4you said:
I think there will be some mess in installed os reflash it after taking a backup.
Click to expand...
Click to collapse
my phone hang while i do a format storage.

maxisgsm said:
my phone hang while i do a format storage.
Click to expand...
Click to collapse
Go twrp recovery and do advance wipe and flash os then.Connect to pc and copy files to memory card and then.Flash it from there since your hang issue will not affect installing.It will solve all problems.Always keep backups before doing anything.

adarshm4you said:
Go twrp recovery and do advance wipe and flash os then.Connect to pc and copy files to memory card and then.Flash it from there since your hang issue will not affect installing.It will solve all problems.Always keep backups before doing anything.
Click to expand...
Click to collapse
every time the phone boot into twrp, it only go back to last state and keep fail then reboot...... it will cycle until battery die. i cannot go anywhere in twrp .....
now i at fastboot state, when i try to flash stock rom, it gave me the error
G:\adbFire>fastboot flash update update_8.zip
sending 'update' (1115283 KB)...
OKAY [ 88.153s]
writing 'update'...
FAILED (remote: partition table doesn't exist)
finished. total time: 88.237s

Your partition got messed by installing custom rom.This problem is uncommon.I cant find good solution for m2 in xda or any forums.Brother just bricked your phone.These cases occur when wrong kernal flash,flashing radio etc.I found this problem only in one plus.
Check these before doing anything in adb
Properly detects the device to avoid errors
Detect if bootloader is locked and temporary unlock it if that is the case.If it temporarly locked again,got to fastboot and unlock it as you know the process.
Try Perform this:
Flashing twrp recovery.img.If no error comes flashing custom or
Twrp is unable to create new partitions...Then
Fastboot boot recovery.img (of stock flyme)
fastboot flash recovery boot.img
Going to stock rom is only nice way i think so.
Boot.img can be found inside rom zip of flyme.Go for flyme first.
It isn't the best method to flash a different rom, but as the cmd implies its perfectly fine for flashing an update of the same rom.Since phone is prime important now.Go back custom then.
Some helpful links linkshttps://forum.xda-developers.com/meizu-m2-mini/how-to/install-stock-recovery-meizu-m2-mini-t3433916
Or wait for any heads to reply:silly:

adarshm4you said:
Your partition got messed by installing custom rom.This problem is uncommon.I cant find good solution for m2 in xda or any forums.Brother just bricked your phone.These cases occur when wrong kernal flash,flashing radio etc.I found this problem only in one plus.
Check these before doing anything in adb
Properly detects the device to avoid errors
Detect if bootloader is locked and temporary unlock it if that is the case.If it temporarly locked again,got to fastboot and unlock it as you know the process.
Try Perform this:
Flashing twrp recovery.img.If no error comes flashing custom or
Twrp is unable to create new partitions...Then
Fastboot boot recovery.img (of stock flyme)
fastboot flash recovery boot.img
Going to stock rom is only nice way i think so.
Boot.img can be found inside rom zip of flyme.Go for flyme first.
It isn't the best method to flash a different rom, but as the cmd implies its perfectly fine for flashing an update of the same rom.Since phone is prime important now.Go back custom then.
Some helpful links linkshttps://forum.xda-developers.com/meizu-m2-mini/how-to/install-stock-recovery-meizu-m2-mini-t3433916
Or wait for any heads to reply:silly:
Click to expand...
Click to collapse
adb cannot detect my devices ..... if i not mistake, last time i unlcock my OnePlus one without any problem, and adb can detect my phone,
now cannot detect ....

@murtaza1326
TWRP 3.2.1.0 is out!
Update the post

rushiranpise said:
@murtaza1326
TWRP 3.2.1.0 is out!
Update the post
Click to expand...
Click to collapse
post updated new latest 3.2.1 TWRP is added @Dinolek TWRP is alread there in his post so I don't think i should repost it here ??
Regards~

how to recovery install meizu m2 mini flyme 6.2.0.0g

thanks sir.. i wanna install this twrp

Pretty good!

[HELP] TWRP, Root, & Custom ROM

Sorry for the post, my question didn't really get answered on the General Q&A Nood Friendly Thread:
Xenophoresis said:
I have Android 9 and August 1, 2020 security patch on it (YouTube was mentioning security patches? dunno why).
I would like TWRP and a future goal of changing to Lineage OS/Tissot.
Which rooting guide can I follow?
( I got confused with the available threads.)
Click to expand...
Click to collapse
After posting, I tried follow this guide thread
I was able to do step 1 which is to unlock but, I don't know if I should still be flashing a Stock Fastboot ROM?
Also there is no link for TWRP, or which version of TWRP I should get...
The last time I rooted something was a Galaxy Note 2 back in 2012-ish so my relevant knowledge is definitely expired.
Please give me a lead on where to find the correct TWRP file and further instructions.

you want step by step guide to flash custom rom?
- You have unlocked bootloader?
- what OS version you are on at the moment ?
Dont worry i will help you in best of my knowledge i have been through what you are going after some time i learned answer question and we will begin

Yes, my bootloader is already unlocked and fastboot was enabled.
OS is stock Android 9, Aug 2020 security patch:
{
"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"
}
No Fastboot ROM (if that is necessary) or TWRP is installed yet.
PS: I do not know where or which TWRP I should be getting for this phone

Xenophoresis said:
Yes, my bootloader is already unlocked and fastboot was enabled.
OS is stock Android 9, Aug 2020 security patch:
No Fastboot ROM (if that is necessary) or TWRP is installed yet.
PS: I do not know where or which TWRP I should be getting for this phone
Click to expand...
Click to collapse
There is a tutorial u can follow on youtube by Vikram, for Pie with August 2020 patch. N u can download what it needs in the description. Its in Indian language but u can follow what he do. Should be okay n safe
Good luck

Lost149ers said:
There is a tutorial u can follow on youtube by Vikram, for Pie with August 2020 patch. N u can download what it needs in the description. Its in Indian language but u can follow what he do. Should be okay n safe
Good luck
Click to expand...
Click to collapse
I was hoping to get instructions or help in English; I've watched his YouTube tutorial in Indian but I was afraid that I'd do something wrong because I didn't understand what he said.

You can follow the instructions provided for LOS:
https://wiki.lineageos.org/devices/tissot/install
Simply exchange the LOS installing part with the ROM of your choice.
Xenophoresis said:
I was hoping to get instructions or help in English; I've watched his YouTube tutorial in Indian but I was afraid that I'd do something wrong because I didn't understand what he said.
Click to expand...
Click to collapse

timeo78 said:
You can follow the instructions provided for LOS:
https://wiki.lineageos.org/devices/tissot/install
Simply exchange the LOS installing part with the ROM of your choice.
Click to expand...
Click to collapse
Thank you, I'm done with the custom rom and root

Sorry for late reply i couldn't login because of xda forum migration process
steps i used:
- install Twrp (download latest version details below)
- download custom rom and gapps (and transfer it into sdcard or internal storage or your phone)
- download Adb/fastboot tool and drivers (download it in windows pc install it details below)
- Install Twrp (download it from https://dl.twrp.me/tissot/) there are 2 files .zip and .img you would need fastboot and adb drivers https://androiddatahost.com/uq6us install adb minimal in location where of your choice copy twrpX.XXXX.img file beside adb/fastboot.exe , from start menu open command prompt right click run as administrator locate to adb/fastboot folder .
Power off your mi a1 when its powerd off hold down volume down and power button until you see fastboot mode on the phone connect it to pc wait for drivers to install let me know if you need in this regard. Inside command prompt run " fastboot devices " if you see device with bunch of numbers below than it means your phone is connected and drivers are working than enter this command " fastboot boot twrpXX.XXXX.img " it will take no more than 5 seconds your phone will turn on into twrp recovery there you can copy twrpxx.xxx.zip file to your internal storage or sd card flash it when its done restart -> Recovery.
Warning: After flashing twrp zip dont restart to system if you do your phone will show you message that phone has been destroyed so dont restart .
- Installing custom roms: download custom rom of your choice transfer it into internal or sd card from twrp install-locate to custom rom .zip file and flash it also keep in mind lots of roms didn't include gapps so you have to download it from opengapps(for android 8-10) and nikgapps(android 11). Flash gapps . Keep in mind after installing custom roms you will lose twrp recovery so if you want twrp at this stage go ahead and install it
- If you want root access download and flash magisk
Its always good practice to keep stock rom and xiaomi flash tool with you just in case if something goes wrong you can reflash stock rom and boot normally.
Let me know if you need help
Cheers

[RECOVERY][3.6.2-12][TOCO][UNOFFICIAL] Stable TWRP - Team Win Recovery Project

{
"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"
}
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch-driven user interface, with no more volume rocker or power buttons to mash. The GUI is also fully XML-driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:​
Touchscreen-driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout and true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
Source Code:​GitHub: https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance: http://gerrit.twrp.me
Hello, this is TWRP, for Xiaomi Mi Note 10 Lite (toco)​
Touch and ADB work
Sideload
Fastbootd
MTP
USB OTG is working
Decryption IS NOT yet supported for A12
Send me a beer: PayPal​
Kernel source: https://bigota.d.miui.com/V13.0.1.0.SFNMIXM/miui_TOCOGlobal_V13.0.1.0.SFNMIXM_b856dc7481_12.0.zip
Telegram group: https://t.me/ahq254chat
Download​https://bit.ly/3t197EP
Installation​Prerequisites: ADB & Fastboot platform-tools
1. Download the recovery from the link above
2. Boot your device into bootloader mode (Power + Volume Up)
3. Open a command window in the folder containing the downloaded recovery
4. Type the following command and hit Enter
fastboot flash recovery TWRP-3.6.2-12-0530-toco-DennisMurimi.img
Click to expand...
Click to collapse
5. Type this command and hit Enter to boot into recovery
fastboot reboot recovery
Click to expand...
Click to collapse
6. Confirm successful installation when you boot into the new TWRP

Reserved

Download links please . . .

cyned said:
Download links please . . .
Click to expand...
Click to collapse
The link is literally right there in the post. Take your time and read through

AndroidHQ254 said:
The link is literally right there in the post. Take your time and read through
Click to expand...
Click to collapse
At time of post all links reverted to a blog, I don't even remember it. Maybe browser issue, my bad.

cyned said:
At time of post all links reverted to a blog, I don't even remember it. Maybe browser issue, my bad.
Click to expand...
Click to collapse
Could have been a derp

hi, after flashing this update the data became encrypted. i was in twrp 3.5.0 before flashing this.

ZeA_Quin said:
hi, after flashing this update the data became encrypted. i was in twrp 3.5.0 before flashing this.
Click to expand...
Click to collapse
A12 data decrytion is not yet supported. Wait for TWRP team to implement that

Great Work Thank you for keeping this Device up to date almost singlehandedly. Really appreciate the work !

Hi, can you suggest me please a video tutorial? (It has not to be toco, but with the same steps). i tried lots of tutorials and nothing worked. I booted to your twrp, but could not flash it.

Any plans to port TWRP 3.7.0 (Android 12.1 branch)?
This new version finally supports Android 12 decryption.

Chris7375 said:
Great Work Thank you for keeping this Device up to date almost singlehandedly. Really appreciate the work !
Click to expand...
Click to collapse
This is possible because of the users coming in to support the work. So if you can join the supporters team, it will help the work continue even for longer

Gloter125 said:
Hi, can you suggest me please a video tutorial? (It has not to be toco, but with the same steps). i tried lots of tutorials and nothing worked. I booted to your twrp, but could not flash it.
Click to expand...
Click to collapse
A video will come on my youtube channel so ensure that you are subscribed

Hello, is it possible to flash SuperSU with this on MIUI 13.0.2.0 even tough the (de-/)encryption is not supported on A12?

ROOT_Neko said:
Hello, is it possible to flash SuperSU with this on MIUI 13.0.2.0 even tough the (de-/)encryption is not supported on A12?
Click to expand...
Click to collapse
Im sorry but im really nervous since i have bad experiences with the sm-a750fn that also had unofficial TWRP and i just want to root my phone but as far as i noticed i cannot access adb in the stock recovery, thus unable to sideload SuperSU.