Database Users

Restore back to Stock Original Motorola Firmware Titan(XT1068) in OneClick

ONE Click Warranty Back
hello Friends This My First Thread on G 2014(Titan)
Now Get Yours Warranty Back In just one Click
No need to rememberer all this such big commands of FastBoot
i gonna present the simplest way to revert back to stock official Roms with both locked and unlocked Boatloader(after flash) which r Provided in the below links
Pls do press thanks If u really liked my work i need it :good:
best simple way in simple one click (action performed)
!!Disclaimer!!
NOTE: I am not responsible for any kind of boot-logo, corrupt partition,bricked devices, dead SD cards,other Issue etc As I am just new to android developing
This process have been tested personally on my device moto g 2104
NOTE :This Will wipe all your data so pls take all yours useful databackup
INSTRUCTION
1) Download and install the Basic Moto Drives in this http://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/97326/p/30,6720,9050
2)Download the required Official Firmware(KitKat,Lollipop) form here https://mega.nz/#F!Q9YHCQzY!dgyvAJ8eNA3t7az4vizwOQ which i have taken Through Original Motorola Firmware Collection[Thread] thanks to @gregor160300
all the Firmware are Official images and are uploaded Recently
3)Download the OneClick Tool zip according to yours need a(locked) and b(Unlocked) form Here
a)restore with locked Boatloader Here https://drive.google.com/open?id=0By-2WiK-9wJqfmlMT3BoMmxqakU0M0lJdDk0OGF3UmVJZWN5eW90a0pIdUtSU3BRb0pxbms
b)restore with unlocked Boatloader Here https://drive.google.com/open?id=0By-2WiK-9wJqfktRWG1wbFJ6S2JnLU5FTFBNUWp2ckRZWnZmMUVfV1hiX3JjUGw0am1LR2s
4)Now Extract the Firmware zip to a Particular Folder at your given location on your PC/Laptop
5)After That Extract the OneClick zip to a Same Folder (Where U have the Extracted the Firmware Files)
6)Boot your Moto G 2014 into FastBoot Mode and plug your Device into your computer (pls Make sure u have all the proper device drivers are installed)
6)Finally Go To the Extracted Folder and u will see OneClick .bat file just click on OneClick
U r done Njoy till its gets Completed
All the Firmware are Official images Your warranty may not Void also u may get Yours Warrenty Back
hope u Enjoy this
PLS DON'T MIRROR THE LINKS
sry for my bad english i will improve
special Thanks to both @ archies20 @gregor160300,Shawn5162 for their thread:laugh::laugh:
Please Do press Thanks button if u really liked My Work i really need it :good:

It's For Indian Version ?

yes u can check this according to the indian baseband

Tried it today and it worked flawlessly, thanks!

heeey thanks 4 the reveiw hope i will come with other thread

so hey guys. i have a moto g 2014 xt1068 dual sim variant. for some reason after unlocking bootloader, flashing TWRP, and flashing an other ROM(blisspop 5.1.1) for some reason my first sim card slot was like not working at all and my second sim doesnt have mobile data only calls. So I flashed stock firmware 5.0.2(RETAILDSDSALL_XT1068_5.0.2_LXB22.46-28_cid7_CFC.xml) but the problem still exists. I dont know what to do :'( any help?

Mike20017 said:
so hey guys. i have a moto g 2014 xt1068 dual sim variant. for some reason after unlocking bootloader, flashing TWRP, and flashing an other ROM(blisspop 5.1.1) for some reason my first sim card slot was like not working at all and my second sim doesnt have mobile data only calls. So I flashed stock firmware 5.0.2(RETAILDSDSALL_XT1068_5.0.2_LXB22.46-28_cid7_CFC.xml) but the problem still exists. I dont know what to do :'( any help?
Click to expand...
Click to collapse
Change both sim slots?

do a clean Install make a try if still not working change the baseband version and check out again if still not working den hope a hardware fix will resolve it

Hello,
First things first: thanks for this great tool! I needed to restore the original firmware and didn't know how to do that. With this tool it's quite simple.
I had only two small problems:
- the first time I've run tour .bat file I seen several commands being executed, all of the m with an OK in the end, but after all process the phone didn't boot, no recovery also. I ran the .bat file a second time and it's OK now.
- another strange thing happened: the boot logo screen reverted to the "unlocked bootloader" screen.
A question: can I flash only the bootlogo screen via adb?

Moto bootloop struck help help
Hello can any senior member plz help me out.
I have unlocked and rooted moto g2 2014 mobile it was working fine.
But I done a stupid thing by editing system file and overwriting it.
Then my phone stuck in boot loader
I can access recovery TWRP i tried to wipe Delvic and cache and factory resetting but it did'nt worked.
Therefore buy following the link i tried to flash with orginal frimware
www droidviewsmoto g 2014 to stock and lock the bootloader
it was not successful again it strucked in boot loop with Android dead symbol in recovery
------>> Then tried to install TWRP recovery it was successful, but unable to install super user.
There fore I tried to repeat the process buy using both sdk windows platfom tools and vfastboot
buy typing command in cmd as mfastboot.exe oem lock begin
and noticed error saying
hab check failed for boot
failed to verity hab image boot
failed to validate boot image
Plz sir can any one help me out plz

yes
yes u can using the img file
follow this instructions to remove the warning instruction
http://www.bhudroid.com/2015/08/remove-unlocked-bootloader-warning-on.html

Kindly First Update yours boot loader Version
Kindly First Update yours boot loader Version
this can be the an issue
and after that cleanly flash the latest TWRP recovery
and Finally any Latest Build Custom Rom
this may Works

Marcelo_RJ said:
Hello,
First things first: thanks for this great tool! I needed to restore the original firmware and didn't know how to do that. With this tool it's quite simple.
I had only two small problems:
- the first time I've run tour .bat file I seen several commands being executed, all of the m with an OK in the end, but after all process the phone didn't boot, no recovery also. I ran the .bat file a second time and it's OK now.
- another strange thing happened: the boot logo screen reverted to the "unlocked bootloader" screen.
A question: can I flash only the bootlogo screen via adb?
Click to expand...
Click to collapse
yes u can using the img file
follow this instructions to remove the warning instruction
http://www.bhudroid.com/2015/08/remove-unlocked-bootloader-warning-on.html

Kindly First Update yours boot loader Version
sudheerkk87 said:
Hello can any senior member plz help me out.
I have unlocked and rooted moto g2 2014 mobile it was working fine.
But I done a stupid thing by editing system file and overwriting it.
Then my phone stuck in boot loader
I can access recovery TWRP i tried to wipe Delvic and cache and factory resetting but it did'nt worked.
Therefore buy following the link i tried to flash with orginal frimware
www droidviewsmoto g 2014 to stock and lock the bootloader
it was not successful again it strucked in boot loop with Android dead symbol in recovery
------>> Then tried to install TWRP recovery it was successful, but unable to install super user.
There fore I tried to repeat the process buy using both sdk windows platfom tools and vfastboot
buy typing command in cmd as mfastboot.exe oem lock begin
and noticed error saying
hab check failed for boot
failed to verity hab image boot
failed to validate boot image
Plz sir can any one help me out plz
Click to expand...
Click to collapse
Kindly First Update yours boot loader Version
this can be the an issue
and after that cleanly flash the latest TWRP recovery
and Finally any Latest Build Custom Rom
this may Works

thnks .......
woow its working great . very simplest way thank u so much
bhu999 said:
heeey thanks 4 the reveiw hope i will come with other thread
Click to expand...
Click to collapse

Can I get OTA update after this ?
I just want to know can I get OTA update after this if Motorola roll out any update in the near future.

mudit56 said:
I just want to know can I get OTA update after this if Motorola roll out any update in the near future.
Click to expand...
Click to collapse
Yes

woow...
wow its working great for me... very simply to use ... am not face any bugs.......... thanks for your work:good:

@bhu999 Thanks it worked awesome.
one question can i get official OTA update from Motorola if i root my device now ??? Because for rooting custom recovery is required and it is impossible to get OTA while on custom recovery. Right ??

yes u can but with stock recovery
just flash the stock recovery to get the available update also
In One Click method u can get the official available update after completing the whole procedure

Stock recovery extraced from BTV-W09C233B019 ROM - untested

Hi M3 users,
I'm a long time lurker and reader on XDA. Now it's time to give something back or at least participate
Following my recent M3 purchase a dugg a bit deeper into this topic and tried to get us the stock recovery for our devices.
I'm not really a dev. I just used the information I found here and in the russian forum where greatslon (thank you guy) is posting his work.
If you find an error in the process please let me know. The files have not been tested in any way. I have no idea if this would even work (encryption and so on).
So I managed to extract the recovery.img file from the chinese rom. This method will also work for the LTE variant.
Maybe @greatslon or @somboons can share their view on the topic or maybe @somboons can even use it in his tool.
Resources
http://4pda.ru/forum/index.php?showtopic=780572&st=120
http://forum.xda-developers.com/showthread.php?t=2433454
http://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
https://play.google.com/store/apps/details?id=com.teammt.gmanrainy.huaweifirmwarefinder
Tools used
Huawei Firmware Finder (Team MT)
Huawei Update Extractor
Download
M3_BTV-W09C233B019_recovery.zip
Process
1. Start firmware finder (did use the android version)
2. Change device to BTV-W09C233
3. Downloaded the firmware B019 for BTV-W09C233 (no firmware for other variants present ATM)
4. Extracted and copied update.app to SD card
5. copy to PC
6. Extract recovery.img and recovery2.img using Huawei Update Extractor
Best regards,
Benjamin

Don't quite understand what's this for. First of all, recovery should be the same version as your ROM. I don't know if their mismatch will immediately lead to some malfunction, but some people on 4pda said they should match. Second - stock recovery's functions are limited to factory reset (wiping data, cache, etc.) and installing OTA updates. Without changing OEMINFO (and it's still unconfirmed), you won't be able to install any OTA except those, intented for your model and region, so again there's no need to install a higher version of recovery than your ROM is. But anyway, thank you for the extraction instruction.
P.S. I think there's no need to flash both recovery and recovery2. Recovery2 can be successfully replaced with TWRP and this combination is really great, cause you can launch TWRP by holding Volume Up button only.
And the only reason why you should keep recovery original is that it doesn't really wipe /data - it also creates some files there like custom.bin, containing your regional settings.

Hi Slavon,
Thanks for your highly appreciated comment. @somboons was looking for a stock recovery so I thought this might help.
Your given information are really helpful. I did not know that you could flash TWRP in recovery2 and replace erecovery Handy information.
I'm pretty new to the Huawei structure so always glad to learn something.
EDIT
A lot of good information can be found here: http://forum.xda-developers.com/honor-7/general/dual-recovery-honor-7-t3308398
Thank you very much,
sselpeelsxx

Giving Back
Benjamin,
I've also been a long time XDA lurker. Most of the devices I have owned were mainstream and thus already had a very active XDA developer community; Even if root had yet to be achieved, there would be hundreds of messages on the topic.
It seems the Mediapad M3 is just getting started. I am a developer of over 20 years, but very little android experience. However, I have recently spent a considerable amount of time (about 50-100 hours) working with the low level ADB protocol source code. And I have rooted and flashed no less than 50 devices, everything from cell phones to Android TV devices to routers.
I'm going to take this device on as my first real dev effort in this arena.
I have a few goals:
1. Get working backups for people that soft-brick or need to revert (including myself).
2. Recompile TWRP for the M3 to confirm greatslon's work, and better understand the process.
3. Release a stock rom that's pre-rooted and cleaned up (not that there was a lot of bloat on my device).
4. Release a custom rom that's not MIUI (perhaps based of CyanogenMod).
Since I have virtually no experience, I am sure these goals are quite lofty and will take some time. But hey, you got to have a plan, and I don't have anything else to work on right now.
Let me know if you want to work on anything together, or if you need any help with anything development related.
- 0D0A

Hey hey 0D0A,
I totally agree with you regarding the backups, I think once the first OTA update is pushed for the EU and US devices we have a good and safe way to go back.
Especially the US owners are struggling with greatslons TWRP version, that's the first thing we should tackle after the backup topic is cleared
I will contact you regarding possible work
Best regards,
Benjamin

can flash twrp via fastboot but get error saying and no recovery
hi, first thanks greatslon for doing the work on m3.
i seem to have succeeded in getting stuck and can't get it to boot into your custom twrp. adb on linux was working fine, but no longer. ditto for fastboot just get "waiting for devices" now. i switched to win10 and installed the hisuite app so i can use fastboot but still no adb. so i have tried to flash recovery and recovery2 but when i try to boot recovery i get error "Func NO: 11 (recovery image) ERROR NO: 2 (load failed)."
i then downloaded your custom rom and tried to flash the boot for that still no luck. i can't use adb so i am not sure how to just flash the custom rom with fastboot without being able to get into any recovery.
i did have this all rooted and working with your twrp but kept having issues with dpi and there was an ota update (b003) which wouldn't apply. so i tried to restore backup and it wen't south from there. basically now can't do much other than see the unlock "can't be trusted" page and bootloader.
any suggestions?

Desperately need stock recovery img, not sure exactly what when wrong, but it is stuck in a horrible boot loop. Tried Benjamin's recovery files and they seem to remove twrp and put it somewhat back to normal, but can only access the emui recovery and that fails to load the files. Put twrp back and tried greatslon's ROMs, they load but goes back to boot loop. Wipe and format everything, install my original backup through twrp recovery, it says it works, but again, back to boot loop... at this point I think I'm dead... any ideas, any word on the official recovery img? anything? Help!!

What device do you have? And what version were you on?

sselpeelsxx said:
What device do you have? And what version were you on?
Click to expand...
Click to collapse
I have the M3, BTV-W09, not sure what version, MM6.0 EMUI 4.1

Anyone have any other ideas on horrendous boot loop?

sselpeelsxx said:
Hey hey 0D0A,
I totally agree with you regarding the backups, I think once the first OTA update is pushed for the EU and US devices we have a good and safe way to go back.
Especially the US owners are struggling with greatslons TWRP version, that's the first thing we should tackle after the backup topic is cleared
I will contact you regarding possible work
Best regards,
Benjamin
Click to expand...
Click to collapse
Hello, I am unlocked, TWRPed, and rooted, but am trying to reverse all of that. My build number is BTV-W09C128B002. Is it safe to download the stock recovery from the OP for my device? Or do I really need the C128 version?

Hello and sorry for the late response, you would need the matching version for your C128 device.
I may be able to extract recovery from an update, I have to look into this tomorrow.
Regards

sselpeelsxx said:
Hello and sorry for the late response, you would need the matching version for your C128 device.
I may be able to extract recovery from an update, I have to look into this tomorrow.
Regards
Click to expand...
Click to collapse
Thanks! I have been able to use the Huawei Extractor to extract a recovery.img from OTA updates, but have been afraid to try flashing it. It has been recommended to hold off on trying that since that recovery.img is from an OTA and not a FULL update. Any thoughts?

[resolved]Unable to flash anything other than twrp

EDITED: Partially resolved... I recovered but now i am stuck on an emui 3.1 with no gsm working. I have a single sim Huawei p8 lite(ALE-L21) the IMEI is unknown baseband version is empty and model name which is supposed to be ALE-L21 is hi6210sft. Build number is also strange: BalongV100R001C50B311. I would like to know if there is any other way to return to a fully functional emui 4.0 and android 6.0 with GSM working(1 sim). Things i've tried: Checking for updates within EMUI updater.
I have a small little problem... I am quite a huawei newb as Samsung rooting was relatively easy.... One day I looked up on google how to root my personal phone Huawei P8 Lite (ALE-L21) with a Vodafone boot up animation but something went wrong.
I downloaded a "rooting kit" with a .bat file specifically for an ALE-L21 but after going through the whole process (boot loader definitely unlocked) and now nothing works except fastboot mode and recovery mode (twrp) when I try to boot up the phone it gives me an error about an unsuccesful boot and system flash while taking me to the rescue mode(very similar to the fastboot mode) I tried to restore the firmware (I do not know if it has to be same version as build number)... via stock recovery and and update.app but the circle kept being stuck at 90%. I also tried to split the update.app file into a boot.img,recovery.img and system.img but sometimes only system.img or boot.img is outputted with the split_updata.pl. When i try to flash something else other than twrp via fastboot it gives me an error saying "FAILED (remote: Command not allowed)"
I would like to know of a 100% efficient way of restoring or reflashing the full stock emui 4.0 android 6.0 firmware including root although a stock rom is preferred.
Thanks
Giorgio G.

Girogio2103 said:
EDITED: Partially resolved... I recovered but now i am stuck on an emui 3.1 with no gsm working. I have a single sim Huawei p8 lite(ALE-L21) the IMEI is unknown baseband version is empty and model name which is supposed to be ALE-L21 is hi6210sft. Build number is also strange: BalongV100R001C50B311. I would like to know if there is any other way to return to a fully functional emui 4.0 and android 6.0 with GSM working(1 sim). Things i've tried: Checking for updates within EMUI updater.
I have a small little problem... I am quite a huawei newb as Samsung rooting was relatively easy.... One day I looked up on google how to root my personal phone Huawei P8 Lite (ALE-L21) with a Vodafone boot up animation but something went wrong.
I downloaded a "rooting kit" with a .bat file specifically for an ALE-L21 but after going through the whole process (boot loader definitely unlocked) and now nothing works except fastboot mode and recovery mode (twrp) when I try to boot up the phone it gives me an error about an unsuccesful boot and system flash while taking me to the rescue mode(very similar to the fastboot mode) I tried to restore the firmware (I do not know if it has to be same version as build number)... via stock recovery and and update.app but the circle kept being stuck at 90%. I also tried to split the update.app file into a boot.img,recovery.img and system.img but sometimes only system.img or boot.img is outputted with the split_updata.pl. When i try to flash something else other than twrp via fastboot it gives me an error saying "FAILED (remote: Command not allowed)"
I would like to know of a 100% efficient way of restoring or reflashing the full stock emui 4.0 android 6.0 firmware including root although a stock rom is preferred.
Thanks
Giorgio G.
Click to expand...
Click to collapse
Your baseband version is empty because the phone still got a MM modem on it, if the TWRP is the only thing you can flash right now try to find a custom EMUI 4.0 ROM for your device (P8 lite) if I'm correct? and try to flash it, after that go back to TWRP and do a factory reset. After that try to fastboot flash boot.img recovery.img abd system.img, if you want bloatware flash cust.img as well. Hope this helps a bit!

eldin_96 said:
Your baseband version is empty because the phone still got a MM modem on it, if the TWRP is the only thing you can flash right now try to find a custom EMUI 4.0 ROM for your device (P8 lite) if I'm correct? and try to flash it, after that go back to TWRP and do a factory reset. After that try to fastboot flash boot.img recovery.img abd system.img, if you want bloatware flash cust.img as well. Hope this helps a bit!
Click to expand...
Click to collapse
Arent the boot.img, recovery.img and system.img the actual rom? if not what format should roms be in? Please note that not all custom roms for customizing the emui 4.0 are supported from emui 3.1. Some links would be really appreciated... so much spam on the internet! I am also worried about trying roms that are made for emui 4.0 and say that the emui 4.0 already installed is a prequisite. Should I?

Girogio2103 said:
Arent the boot.img, recovery.img and system.img the actual rom? if not what format should roms be in? Please note that not all custom roms for customizing the emui 4.0 are supported from emui 3.1. Some links would be really appreciated... so much spam on the internet! I am also worried about trying roms that are made for emui 4.0 and say that the emui 4.0 already installed is a prequisite. Should I?
Click to expand...
Click to collapse
boot.img> Kernel
recovery.img> Recovery lol
system.img> the actual system
Aren't you on marshmallow before you downgraded to lollipop? If you were, modem of MM is not compatible with lollipop hence IMEI and baseband are empty now for you. Search for EMUI custom ROM's to flash thru TWRP (not CyanogenMod). Also, you're in a wrong forum because this is P8 strictly, here are threads for your phone: https://forum.xda-developers.com/p8lite :good:

eldin_96 said:
boot.img> Kernel
recovery.img> Recovery lol
system.img> the actual system
Aren't you on marshmallow before you downgraded to lollipop? If you were, modem of MM is not compatible with lollipop hence IMEI and baseband are empty now for you. Search for EMUI custom ROM's to flash thru TWRP (not CyanogenMod). Also, you're in a wrong forum because this is P8 strictly, here are threads for your phone: https://forum.xda-developers.com/p8lite :good:
Click to expand...
Click to collapse
Thanks I tried what you said in your previous reply but another problem came. I installed an android 7.1.1 custom rom but now GSM doesn't work. SIM card would already be in the tray in the phone but it is not detected. Why would I need a phone which isn't a phone? Now i'll post another issue on the proper thread. The android worked fine. I don't know if anybody knows of a huawei emergency software recovery as samsung does... HiSuite only has 4 devices available for emergency software recovery. Also original links on huawei website have disappeared and huawei links for stock rom on xda are also temporarily removed.
:good:
Thanks,

Girogio2103 said:
Thanks I tried what you said in your previous reply but another problem came. I installed an android 7.1.1 custom rom but now GSM doesn't work. SIM card would already be in the tray in the phone but it is not detected. Why would I need a phone which isn't a phone? Now i'll post another issue on the proper thread. The android worked fine. I don't know if anybody knows of a huawei emergency software recovery as samsung does... HiSuite only has 4 devices available for emergency software recovery. Also original links on huawei website have disappeared and huawei links for stock rom on xda are also temporarily removed.
:good:
Thanks,
Click to expand...
Click to collapse
I told you to flash custom EMUI rom, not CyanogenMod. Now u need to fastboot flash the stock firmware, after that do a factory reset to get your sim functionality back.

Thanks anyway... I resolved this by flashing an emui 4 based custom ROM and I got SIM back plus root(kangvip). Also did a nandroid backup now that everything works good. Btw I never flashed Cyanogen mod ?.
Not sure if it's worth it to go back to stock now...

Girogio2103 said:
Thanks anyway... I resolved this by flashing an emui 4 based custom ROM and I got SIM back plus root(kangvip). Also did a nandroid backup now that everything works good. Btw I never flashed Cyanogen mod .
Not sure if it's worth it to go back to stock now...
Click to expand...
Click to collapse
well, you said "I installed an android 7.1.1 custom" having in mind 7.1.1 is basically cyanogenmod/RessurectionRemix/OpenKirin... those are not official. And yeah, that rom that you're on right now is also official but with some tweaks/optimisations/modifications so you dont have to worry

eldin_96 said:
well, you said "I installed an android 7.1.1 custom" having in mind 7.1.1 is basically cyanogenmod/RessurectionRemix/OpenKirin... those are not official. And yeah, that rom that you're on right now is also official but with some tweaks/optimisations/modifications so you dont have to worry
Click to expand...
Click to collapse
Ok... Now to install other Roms how do I know if they are official and will work?

help me
TWrp message
message came to me
say
E: primary block device /dev/block/mmcb1kop8
for mount point /data is not present
failed to mount data
unable to create /data/media folder
when i install zip or wipe or format (yes) or do any thing told me failed to mount data

Xiaomi Mi9T Hard/Rock Bricked

Hello everyone i am in desparate need of some guidance where i unfortunately Hard bricked my Mi9t while trying to flash the new Mokee Rom.
Where i think i went wrong was wiping the system option in twrp. After reboot i was stuck on flashboot and unable to get back into twrp recovery.
I then proceeded to flashboot twrp, also used multiple versions of twrp, again to hopefully be able to get into twrp recovery with no prevail.
Also tried to fastboot via Miflash tool with all latest fastboot roms available currently but kept getting a anti-rollback error.
So then i searched a way to install recovery or stock rom manually via flashboot commands. This caused me to end up where im at, no fastboot, no recovery, no logo at all. I connect the usb and the phone wont turn on at all, just a dead phone. Power button completely unresponsive now, Vol-Up/Vol-Down + Power and nothing.
I worked on it for countless hours trying to simply get into fastboot now with huge anxiety thinking i killed my phone.
I left my phone to charge all night and woke up this morning trying to get into fastboot again and nothing again.
Can someone please lead me in the right direction???
Everywhere i look the info seems to be outdated. At this point i am willing to send it in for repairs but i live in Indiana, US and there isnt a Xiaomi Service location anywhere in site.

Sad story. What did you do in fastboot? If you can't flash a certain twrp version you would have to do:
1. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (in twrp archives)
2. fastboot erase recovery
3. fastboot flash recovery your-twrp.img
Concerning AntiRollBack:
You can bypass ARB in miflashtool, set the number of your new rom higher or edit the batch/shell-files manually. The first few lines are ARB and device-check.
I know the info comes too late, but maybe someone reads this before trying things the way you did. There have to be some EDL-pins inside the phone to reflash fastboot but you would have to open your phone. My opinion/solution: Cry and send in.
Anyway: Can you tell us what you did to wipe fastboot?

fabsen said:
Sad story. What did you do in fastboot? If you can't flash a certain twrp version you would have to do:
1. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (in twrp archives)
2. fastboot erase recovery
3. fastboot flash recovery your-twrp.img
Concerning AntiRollBack:
You can bypass ARB in miflashtool, set the number of your new rom higher or edit the batch/shell-files manually. The first few lines are ARB and device-check.
I know the info comes too late, but maybe someone reads this before trying things the way you did. There have to be some EDL-pins inside the phone to reflash fastboot but you would have to open your phone. My opinion/solution: Cry and send in.
Anyway: Can you tell us what you did to wipe fastboot?
Click to expand...
Click to collapse
When i 1st attempted to recover twrp i used TWRP 3.1.1-2 fixed from 4PDA. Ran the .exe file and the prompt said both fires installed successfully, but when i did a reboot it wouldnt go into twrp anymore, just stuck in logo so i would end up back in bootloader.
ttp://en.miui.com/thread-942449-1-1.html
This is exactly the instructions i tried to use before i lost fastboot.
At one point while entering the commands, it froze then my phone completely died and could never make it do anything else.

Why the hell did you use an outdated tutorial for an other phone? A few of the commands also wouldn't work because there are only some of these partitions. But if you did it with the right firmware it shouldn't brick anyway. So maybe you were stuck at boot flash. Else you still would be able to boot into fastboot.#
I feel sorry for you bro but it looks like you were searching for a possiblity to brick your phone

fabsen said:
Why the hell did you use an outdated tutorial for an other phone? A few of the commands also wouldn't work because there are only some of these partitions. But if you did it with the right firmware it shouldn't brick anyway. So maybe you were stuck at boot flash. Else you still would be able to boot into fastboot.#
I feel sorry for you bro but it looks like you were searching for a possiblity to brick your phone
Click to expand...
Click to collapse
I kno bro i felt like shyt believe me. Literally all day in panic and anxiety that i just wasnt thinking straight and using any kind of guide i can find and ended up here.
Made some progress today tho.
Since my device manager or MiFlash tool wasnt recognizing my device even when i installed Qualcom drivers and pushing all sorts of buttons lol,
I have now opened her up for some surgery and using the Test-Point EDL method.
https://i.postimg.cc/HWJGWHRw/test-point-redmi-k20-mi-9t.png
While USB connected and shorted these 2 pins my computer finally recognized my device in MiFlash Tool and Device Manager again as Qualcomm HS-USB QDLoader 9008 (COM3)!!!
Now the next problem is the MiFlash tool. I tried to flash rom and status states cannot receive hello packet. From what i understand, i need an authorized account.
Only thing i could find to bypass this was this but currently not yet working. - https://forum.xda-developers.com/mi-8/how-to/unbrick-mi8-edl-authorized-account-t3896677
Any ideas where to go from here?

https://mi-globe.com/unbrick-your-xiaomi-phone-without-authorized-mi-account/
https://c.mi.com/thread-1479882-1-0.html
I didn't need an authorized account last year but maybe they've changed something. The guides are up to date so maybe follow these steps.

fabsen said:
https://mi-globe.com/unbrick-your-xiaomi-phone-without-authorized-mi-account/
https://c.mi.com/thread-1479882-1-0.html
I didn't need an authorized account last year but maybe they've changed something. The guides are up to date so maybe follow these steps.
Click to expand...
Click to collapse
Already ran into those sites and actually am currently trying out S-Unlock service to bypass Authorized Account with there XiaomiTool v0.01, and unfortunately again with no prevail.
https://imgur.com/gallery/WMt968b
As you can see i got passed Hello packet, but now it doesn't go passed this message or looks like it didnt do anything.
https://imgur.com/gallery/hHApyJL
Already contacted S-Unlock Admin and now waiting for response. Im assuming im using the right Flashboot Roms. Tried latest flashboot roms from here available. https://xiaomifirmwareupdater.com/miui/davinci/
I also emailed unbrick.ru if they support K20/Mi9T variant and waiting for there reply.

Firmware on your page is not up to date. Use https://mifirm.net/
What device do you have? EEA/Global/CN? And what flashfiles did you use? I'm asking this because the only way I know to brick your device is to flash global/eea-rom on chinese device and lock the bootloader.

fabsen said:
Sad story. What did you do in fastboot? If you can't flash a certain twrp version you would have to do:
1. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (in twrp archives)
2. fastboot erase recovery
3. fastboot flash recovery your-twrp.img
Concerning AntiRollBack:
You can bypass ARB in miflashtool, set the number of your new rom higher or edit the batch/shell-files manually. The first few lines are ARB and device-check.
I know the info comes too late, but maybe someone reads this before trying things the way you did. There have to be some EDL-pins inside the phone to reflash fastboot but you would have to open your phone. My opinion/solution: Cry and send in.
Anyway: Can you tell us what you did to wipe fastboot?
Click to expand...
Click to collapse
Hey,
I'm in a similar boat but I still have fastboot.
I can flash everything I wan't. But flashing a recovery doesn't do anything.
I can not boot into the recovery.
When I boot into the recovery i'm at the bootloop screen.
My PC does recocgnize it as recovery mode tho.
Anyways is there a way to get out of this mess? I wanted to try to flash with miflash over fastboot.img but I can't find any .img to flash.
All I can find are the .zips for twrp.
I didn't want to flash cfw tho. I got into the mess because there was an update today for stock rom and I flashed it with twrp. Because OTA didn't work.
/edit
I found the fastboot files.
But how do I bypass the antirollback error

Waidowai said:
Hey,
I'm in a similar boat but I still have fastboot.
I can flash everything I wan't. But flashing a recovery doesn't do anything.
I can not boot into the recovery.
When I boot into the recovery i'm at the bootloop screen.
My PC does recocgnize it as recovery mode tho.
Anyways is there a way to get out of this mess? I wanted to try to flash with miflash over fastboot.img but I can't find any .img to flash.
All I can find are the .zips for twrp.
I didn't want to flash cfw tho. I got into the mess because there was an update today for stock rom and I flashed it with twrp. Because OTA didn't work.
/edit
I found the fastboot files.
But how do I bypass the antirollback error
Click to expand...
Click to collapse
https://mifirm.net/model/davinci.ttt
to bypass the ARB you can edit the batch/shell files. the first few lines are device-check and ARB. you can also use xiaomitool and select it there.
Edit: I had the same problem with a twrp version I had installed. After switching to russian version I couldn't downgrade twrp. Just try one of the other 2 versions available.

fabsen said:
https://mifirm.net/model/davinci.ttt
to bypass the ARB you can edit the batch/shell files. the first few lines are device-check and ARB. you can also use xiaomitool and select it there.
Edit: I had the same problem with a twrp version I had installed. After switching to russian version I couldn't downgrade twrp. Just try one of the other 2 versions available.
Click to expand...
Click to collapse
I've had the russian version of twrp that didn't allow backups.
I know tried all the other version as well.
What happens is it stays in mi.com unblocked screen and my pc will recognize that it's in recovery but twrp never opens.
Like I said the normal stock recovery is flashable but all other twrp versions don't work for some reason.
I've tried all 3.
I know where the lines are but idk what to write in there.
I tried to just delete the lines and then I've got a different error.
Also when changing the version number it says success it actually flashes for 0 seconds and nothing happens.

Waidowai said:
I've had the russian version of twrp that didn't allow backups.
I know tried all the other version as well.
What happens is it stays in mi.com unblocked screen and my pc will recognize that it's in recovery but twrp never opens.
Like I said the normal stock recovery is flashable but all other twrp versions don't work for some reason.
I've tried all 3.
I know where the lines are but idk what to write in there.
I tried to just delete the lines and then I've got a different error.
Also when changing the version number it says success it actually flashes for 0 seconds and nothing happens.
Click to expand...
Click to collapse
The russian version I've installed allows backups, tried allready.
You can simply remove the lines, just care you dodn't left something or delete too much. Use xiaomitool v2, it'll bypass the lines.

fabsen said:
The russian version I've installed allows backups, tried allready.
You can simply remove the lines, just care you dodn't left something or delete too much. Use xiaomitool v2, it'll bypass the lines.
Click to expand...
Click to collapse
If i download the xiamitool v2 and choose my device is bricked it says feature is not available yet.
/edit
If I choose mod the phone it says my phone serial and all the 3 other things are unknown.
if I select my phone my phone reboots and says waiting for debugging mode....
Then if I delete the ARB lines and try to flash via MiFlash it says error error no such file found
Can someone pls give me some clearer instructions.

Ok I somehow fixed it.
I flashed everything manually like the times before twrp existested.
Now I don't have the OS running but a running twrp.
I could flash xiaomi eu now and be done with it. But I actually wanted to use stock rom and not a costume rom right now because I wanted to switch to a costume rom when a good official comes out whenever that is.
Although flashing the stock rom got me in this mess in the first place. I never had this problem with flashing costume roms.
Anyhow I know this might not be the place to ask but are xiaomi eu and stock actually that different? Also are there any downsides in using it over stock?
My experience on most phones was that early costume roms usually didn't work with all features etc.
/edit
alright who gives a dang I just flashed the eu rom to be safe with updates..
anyhow is it normal that my devices says Redmi by Xiaomi now?
Prior on my stock rom it said MI by mi.com or something

Waidowai said:
Ok I somehow fixed it.
I flashed everything manually like the times before twrp existested.
Now I don't have the OS running but a running twrp.
I could flash xiaomi eu now and be done with it. But I actually wanted to use stock rom and not a costume rom right now because I wanted to switch to a costume rom when a good official comes out whenever that is.
Although flashing the stock rom got me in this mess in the first place. I never had this problem with flashing costume roms.
Anyhow I know this might not be the place to ask but are xiaomi eu and stock actually that different? Also are there any downsides in using it over stock?
My experience on most phones was that early costume roms usually didn't work with all features etc.
Click to expand...
Click to collapse
Basically it's (xiaomi.eu) debloated and optimized but sadly based on chinese official rom. That means no widevine L1.
In my opinion the best rom is EEA (because of "spy restrictions"), debloated with ADBTools with same optimizations which come with mi-globe rombuilder (gpsset, preinstalled magisk, adaway, removed apps). Sadly mi-globe is based on xiaomi.eu which is based on chinese official.

Waidowai
Could you explain the steps you did to flash ALL manual? Which Commands? Which imagens?
Thanks friend.

fabsen said:
Basically it's (xiaomi.eu) debloated and optimized but sadly based on chinese official rom. That means no widevine L1.
In my opinion the best rom is EEA (because of "spy restrictions"), debloated with ADBTools with same optimizations which come with mi-globe rombuilder (gpsset, preinstalled magisk, adaway, removed apps). Sadly mi-globe is based on xiaomi.eu which is based on chinese official.
Click to expand...
Click to collapse
Well i did instal xiaomi.eu now. Not because of optimizations etc.
The only reason is that like i said i don't wanna brick by updating official roms anymore.
I mean maybe it's my bad since I'm running costume roms on all my phones for about 12 years or longer.. can't remember when I started but I think with first xyanogen mod.
And I don't know how to flash stock roms.
But with a costume rom it won't brick and if it does I'm not loosing twrp again.
For debloating I do that myself with the android terminal. So idk what the rom has on bloat I'll just uninstall it.
My only fear was that main features don't work with the costume rom. But from first sight everything but themes work fine. And I couldn't care less.
Well one thing changed the icons look like a chineese appleish phone now. Oh well I'll change that later.
Other than that the fingerprint is more responsive which I do like.
And for some reason my Modelnumber changed from Mi 9T to RedmiK20. Even on the boot it says Redmi now instead of MI.
Idk if it's because of the ROM or because I manually flashed the phone.
---------- Post added at 02:51 PM ---------- Previous post was at 02:42 PM ----------
mauriciocardoso said:
Waidowai
Could you explain the steps you did to flash ALL manual? Which Commands? Which imagens?
Thanks friend.
Click to expand...
Click to collapse
Just download the fastboot rom and flash everything but dummy. You can flash dummy to but that is just for ARB. Depending on what your ARB index is you can flash it to ignore future problems.
My index was 1 tho and apperently if it's under 4 ARB is supposed to be irrelavent.
I'm not to sure on ARB tho because it's my first time dealing with ARB.
Other then that u flash everything else.
You will end up with a phone that is empty. Basically you reformate your phone so nothing is on there but TWRP. My phone was at 59gb/60 or something like that. basically the only folder I've had left was twrp.
Like I said I remembered the method from like 8 years ago when we didn't have twrp.
The problem with this method is that you can easily hardbrick tho I think. Since if it doesn't work you turned your phone into a fancy usb drive.
I only did it because I thought of buying a new one so since the phone was dead in my eyes already I just tried the old method and it worked fine, besides rebranding the phone to RedmiK20 from Mi9T.
Anyhow if your not giving up on the phone yet I wouldn't try it. Only try if you wanna throw the phone in the trash anyways.

just like me , for the anti roll issue u need to flash newers rom like from latest u flash on ur device before (recommend V10.3.11.0.PFJMIXM) u can get on mifirm.net . after download rom extract the file into fastboot tools then copy all .img file into fastboot tools . after that open the fastboot mode on ur phone and tools on pc
then flash this file
fastboot flash dtbo dtbo.img
fastboot flash logo logo.img
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash misc misc.img (u can get on fastboot rom not .zip)
fastboot flash recovery recovery.img (recommend used twrp-3.3.1-2-davinci-fix)
then try reboot phone into recovery
if work let me know . im trying make this method because before this i got this problem to after flashing paranoid rom without format data .

Waidowai said:
Well i did instal xiaomi.eu now. Not because of optimizations etc.
The only reason is that like i said i don't wanna brick by updating official roms anymore.
I mean maybe it's my bad since I'm running costume roms on all my phones for about 12 years or longer.. can't remember when I started but I think with first xyanogen mod.
And I don't know how to flash stock roms.
But with a costume rom it won't brick and if it does I'm not loosing twrp again.
For debloating I do that myself with the android terminal. So idk what the rom has on bloat I'll just uninstall it.
My only fear was that main features don't work with the costume rom. But from first sight everything but themes work fine. And I couldn't care less.
Well one thing changed the icons look like a chineese appleish phone now. Oh well I'll change that later.
Other than that the fingerprint is more responsive which I do like.
And for some reason my Modelnumber changed from Mi 9T to RedmiK20. Even on the boot it says Redmi now instead of MI.
Idk if it's because of the ROM or because I manually flashed the phone.
---------- Post added at 02:51 PM ---------- Previous post was at 02:42 PM ----------
Just download the fastboot rom and flash everything but dummy. You can flash dummy to but that is just for ARB. Depending on what your ARB index is you can flash it to ignore future problems.
My index was 1 tho and apperently if it's under 4 ARB is supposed to be irrelavent.
I'm not to sure on ARB tho because it's my first time dealing with ARB.
Other then that u flash everything else.
You will end up with a phone that is empty. Basically you reformate your phone so nothing is on there but TWRP. My phone was at 59gb/60 or something like that. basically the only folder I've had left was twrp.
Like I said I remembered the method from like 8 years ago when we didn't have twrp.
The problem with this method is that you can easily hardbrick tho I think. Since if it doesn't work you turned your phone into a fancy usb drive.
I only did it because I thought of buying a new one so since the phone was dead in my eyes already I just tried the old method and it worked fine, besides rebranding the phone to RedmiK20 from Mi9T.
Anyhow if your not giving up on the phone yet I wouldn't try it. Only try if you wanna throw the phone in the trash anyways.
Click to expand...
Click to collapse
Don't know how you manage to brick your phone with official firmware tbh. And why should you lose TWRP? I flashed about 10 times (global, eea, chinese, xiaomi.eu, mi-globe) and I still didn't have to reflash twrp once. It won't even touch the recovery partition. I also don't see a reason to mess with fastboot (except your brick haha). The boot behavior (redmi instead of mi) is fine, depends on the rom you've flashed. If you flash global or eea rom it'll switch back to "Mi".
What do you mean by "I don't know how to flash official rom"? Boot up twrp, clean dalvik cache/cache, install... tadaaa. I was also using custom roms on all of my phones but I can't find a reason for now to do so. I see only bugs and things not working. I want my widevine L1 and I want AndroidAuto to be working. I'll stay on global/eea till a good rom pops up.

fabsen said:
Don't know how you manage to brick your phone with official firmware tbh. And why should you lose TWRP? I flashed about 10 times (global, eea, chinese, xiaomi.eu, mi-globe) and I still didn't have to reflash twrp once. It won't even touch the recovery partition. I also don't see a reason to mess with fastboot (except your brick haha). The boot behavior (redmi instead of mi) is fine, depends on the rom you've flashed. If you flash global or eea rom it'll switch back to "Mi".
What do you mean by "I don't know how to flash official rom"? Boot up twrp, clean dalvik cache/cache, install... tadaaa. I was also using custom roms on all of my phones but I can't find a reason for now to do so. I see only bugs and things not working. I want my widevine L1 and I want AndroidAuto to be working. I'll stay on global/eea till a good rom pops up.
Click to expand...
Click to collapse
I mean yeah that's what i thought just flash a official rom like any stock rom. Or rather if you change roms cuz if you update existing roms you don't really need to wipe anything anymore.
But apperently it busted my whole phone. It was a weird brick. My phone wasn't recognized as a phone anymore in fastboot. But it was recognized normal in adb. So I needed to change windows drivers to make my phone recognize.
And after that nothing booted but stock recovery and even then it said I don't have debugging enabled. Eventho I was connected to adb??
Anyhow I think the flash messed up the whole system partition. So what I did is in short formate the whole drive and start with a clean slate.. anyhow don't need to repeat all that.
But yeah I'm with you with the take on costume roms. I don't see the need anymore since most stock roms are decent nowadays and costume roms especially are most likely buggy somehow. Good thing is that most stuff I need in my phone is working on the eu rom. Like I said only thing that I could find not working are themes. But thats ok.
I don't know what that widevine L1 thing is. So I prolly don't need it. But maybe u can explain it to me Always up to learn new things.
Well for now I stick with the costume rom since it's basically no different to me. And the chance of bricking again like that with a costume rom are slim to none. If the phone brick it's most likely just a simple brick that can be fixed with twrp. and if that doesn't work by booting into twrp from adb.
Btw that didn't work on my weird brick either. I couldn't boot anything from adb. It gave me a black screen when trying to boot something.
Anyhow I'm glad I've got it running again. But somehow I'm not that surprised. Most times when I brick phones I can fix it when I'm at the point where I wanna throw the phone away. Cuz then I'm just flashing everything I can to make it work xD.

(SOLVED) I used TWRP and accidentally wrote over the boot recovery partition

Hello,
In a late-night act of utter stupidity, when over-tired, I re-flashed the boot recovery with TWRP and bricked my M3. It obviously can't now enter boot recovery.
I've used TWRP and successfully re-flashed custom roms on my original Mate, and changed regions. (Not in any way an expert, I know how to follow instructions.)
I was trying to convert my Chinese (I was living there) ROM to UK. It's tricky nowadays.
This was a stupid error when tired. Any way back?
I read somewhere that people with the right hardware can do it, but finding someone. I'm in Leeds, UK.
The pad does (did) what I need, and I'm not in a position to buy a new one. If it's dead, it's dead; and I can move on.
Cheers in advance for any input.
SOLVED
See my last post on this thread.
After using Multi Tool V8 to enquire into the machine I switched off and rebooted.
It came back with a "Wipe cache" and "Reset to factory settings" Huawei screen, so I did both and - It booted!
It had spectacularly failed to do anything but boot-loop since coming out of a very dead battery yesterday.
1) Boot recovery, OTA recovery, and dload recovery from SD were all unavailable after the original overwriting of the bootloader.
2) After being dead for months, all recovery options booted from power button plus vol- Vol+ and Vol+/- - but still bootlooping.
Then, suddenly it booted into wipe cache/factory reset screen.
Android 7, EMUI 5.1.3
I have no idea why.
Now fully working. (Including restarting)

I fell in a similar situation after having flashed a magisk module .. unfortunately my nandroid backup didn't restore my devices, but I was able to enter in twrp recovery.. so,..
if you can boot in twrp recovery, not all hopes are lost..
first of all, you must download a stock firmware for your device (i suggest to download trough huawei firmware finder: https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146/amp/)
You must download a fullota version of stock firmware
then, you can flash this firmware (3 zip files) trough hurupdater via twrp recovery: https://forum.xda-developers.com/ho...lash-official-firmware-recovery-t3769279/amp/
in order to not overwrite twrp recovery, put the twrp.img file in the same folder and rename it to recovery.img
you can find more info in this topic (follow the instructions, in particular those on how to use hurupdater): https://forum.xda-developers.com/me...ting-btv-dl09-to-unapproved-firmware-t3817541
in order to find a firmware suitable to your device, try to find info on it: you have a mediapad m3 European? American? asian? just wifi or also 4G-LTE (whit a sim and phone functions)? lite or normal version? 10 inches or 8.4?
everyone of these devices have different codenames and suitable firmwares
I found exact firmware for my devices with the procedure described here:
https://forum.xda-developers.com/showpost.php?p=77241673&postcount=3
.. but, if you flashed a wrong firmware, i really don't know if it might help you..
anyway, i wish the info above could help you.

qllkevuoi said:
I fell in a similar situation after having flashed a magisk module .. unfortunately my nandroid backup didn't restore my devices, but I was able to enter in twrp recovery.. so,..
if you can boot in twrp recovery, not all hopes are lost..
first of all, you must download a stock firmware for your device (i suggest to download trough huawei firmware finder: https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146/amp/)
You must download a fullota version of stock firmware
then, you can flash this firmware (3 zip files) trough hurupdater via twrp recovery: https://forum.xda-developers.com/ho...lash-official-firmware-recovery-t3769279/amp/
in order to not overwrite twrp recovery, put the twrp.img file in the same folder and rename it to recovery.img
you can find more info in this topic (follow the instructions, in particular those on how to use hurupdater): https://forum.xda-developers.com/me...ting-btv-dl09-to-unapproved-firmware-t3817541
in order to find a firmware suitable to your device, try to find info on it: you have a mediapad m3 European? American? asian? just wifi or also 4G-LTE (whit a sim and phone functions)? lite or normal version? 10 inches or 8.4?
everyone of these devices have different codenames and suitable firmwares
I found exact firmware for my devices with the procedure described here:
https://forum.xda-developers.com/showpost.php?p=77241673&postcount=3
.. but, if you flashed a wrong firmware, i really don't know if it might help you..
anyway, i wish the info above could help you.
Click to expand...
Click to collapse
Thanks for the reply, and sorry for the delay. New child has somewhat taken over our lives!
I'll take a look at the tablet again when I have time, probably next month.

Update - Bootloader working after battery drain: Now what?
[Edit] Post redundant as it started working - see OP.
NwotNot said:
Thanks for the reply, and sorry for the delay. New child has somewhat taken over our lives!
I'll take a look at the tablet again when I have time, probably next month.
Click to expand...
Click to collapse
Well...
After being without power for so long I turned the tablet on and it booted!
However, it then went into OTA and updated - rebooted - and locked the damned bootloader.
1) It's showing as rooted.
2) Boot loader is locked.
3) Fastboot & rescue mode comes up.
4) Recovery (OTA) still comes up but "Fails" this time.
I don't recall how I unlocked it last time. I don't ever rememebr an unlock code.
Status:
Fastboot reports it exists.
ADB reports "Null" not found. (ADB drivers installed).
Firmware version: CPN-AL00C233B078
Device name: CPN-AL00
Serial Number: Showing
IMEI: Showing
Bootloader state: LOCK
I have an old TWRP backup - don't know how to use it.
Solutions?
a) Any kind devs prepared to work with me and find the boot unlocker code for this 5-year old tablet?
b) Any other solutions now we know what's what?
I'm self employed without income in this pandemic and can't really afford to buy a new tablet. If I have to, it won't be Huawei.
(There's a T3 10.6" at £89, but I'm not biting - I need to sort out a budget tablet with at least the oomph of the M3.)
Any help much appreciated. :good:
David.