Database Info

Soft bricked MHA-L29C432; please help!!!!

Hi guys i was trying to install a custom rom on my mate 9 (MHA-L29C432-156)so i followed the instructions ; unlocked the bootloader; then installed twrp 3.1.0-0; on twrp formated data; then full wiped and try to install AurRom from SD; but get a message that zip file is corrupted; so I tried with S.H.I.E.L.D ROM and it flashed , but then when boot goes to eRecovery, and give me 3 options download latest version and recovery; reboot and shutdown. So now I cant boot the phone, when I restarted, followed same steps , format data, full wipe and trying to installing again but getting a message about all zip files of the roms are corrupted; then i try to restore backup; and same again get the huawei logo, then the android logo , phone restarts and eRecovery again.
Please someone HELP, I use this phone for my work...........!!!!!!!!!

How did you full wipe?
Also try with Twrp 3.0.2-2
Here:www.androidfilehost.com/?fid=745425885120697579

dannytgt said:
on twrp formated data
Click to expand...
Click to collapse
Something went wrong here. You can run 'adb logcat' to see the crash details while starting.

If you have a backup on twrp then restore to get phone working. You may need to flash the public and hw-data zips afterwards though.
If you don't have a backup then you could try flashing the C636 off line firmware and then use firmware finder to go back to your original firmware
Sent from my MHA-L09 using XDA-Developers Legacy app

you may just flash the modified recovery ( See Guide subforum ) ) to bypass the update certification and authorization and reflash an original firmware. your stored files will be lost anyway in most cases.
I would bet superuser ( shield ) and SuperSU ( Aurom) messed your boot image. Both are incompatible to each other and, afaik both are incompatible to twrp 3.1.
Flash TWRP 3.0.2.2, reboot to recovery again to change version, flash the rom ( f.e. shield rom), boot once up, reboot to recovery and THEN you may flash twrp 3.1

Thanks all of you guys, I've solved the problem, it seems that's something related to the sd card, I've formated the sd and transfer the files trough another phone and then put the sd on the mate 9, I follow the steps as followed before and works successfully, now I'm on AurRom and 182 firmware.

Hanging during Boot animation

Hello, I would like some help since I got this device just yesterday.
I got it with the EMUI 4 Android 6.0 stock installed on it. Since there was no update for it I unlocked the bootloader installed twrp rooted and manually flashed EMUI 5 7.0. Everything worked fine.
I created a backup through TWRP and restored it succefully multiple times.
Then I installed the Meticulus TWRP (since I was told it is a prerequisite for the AOSP). I Flashed the AOSP but it stuck during the boot animation (30 minutes afterwards I powered it off).
I reflashed my old TWRP and tried restoring my backup. IT fails with the explanation "Cannot wipe /vendor" while at the top it says "Cannot mount /vendor (invalid argument)" "Cannot mount /product (invalud argument)".
Anyone has a clue how to fix this? Fastboot adb all works so there should be a way to boot into an OS properly?

Since AOSP was not booting i guess you forgot formatting /data partition to ext4... And did u Used Stock vendor and not openkirin ones ?
Gesendet von meinem Honor 6X mit Tapatalk

As said I have replaced the custom TWRP with the default one so I think this should not apply anymore?
The "cannot mount vendor/product" messages came from the default TWRP after I reflashed it again.
At the top it says "cannot mount /vendor" either so I guess that is the actual problem?
It would be nice to get teh AOSP up but I really want to be able to boot into something first honestly.
And did u Used Stock vendor and not openkirin ones
Click to expand...
Click to collapse
Can you please explain? When I flashed your ROM i was on your TWRP. Does this even matter anymore?
At best I would be able to restore my backup.

To me it appears to be caused by the vendor partition.
Is there any way I can manually create that through TWRP?

algg said:
To me it appears to be caused by the vendor partition.
Is there any way I can manually create that through TWRP?
Click to expand...
Click to collapse
Yes you can but not creating it through twrp, but flashing it by fastboot mode: this is because
image (.img) files needs to be flashed by fastboot mode to avoid any kind of problem.
So, you should look for the last version of stock firmware on which you was before going custom, like BLN-L21CXXXB368 for example; tell me your build number and I'll find the package for you. Then, extract from the UPDATE.APP (a very big file that contains every partition in your phone like recovery, vendor, data, ecc. - you'll find this file inside the zip archive that contains the downloaded update) the vendor.img using Huawei Update Extractor, and then flash it through fastboot mode using the command "fastboot flash vendor vendor.img".
Otherwise, you could rely on dload method to reflash a full update package, and this should really fix everything since that it'll be like a new and clean installation of the OS. Then, unlocking the bootloader again and reflash TWRP to finally restore your previous backup made when it was working would be the final step.
Feel free to ask for further help

Thanks for the reply first really appreciate it.
I got the device on EMUI 4 Marshmallow rooted it and unlocked the bootloader then installed the BLN-L21C185B140 which worked smoothly.
I used that update.zip and extracted into dload root folder and started the huawei recovery installer but it said "package not found".
I tried flashing something to vendor before with fastboot but it said command not allowed.
Maybe I am doing something wrong?

algg said:
Thanks for the reply first really appreciate it.
I got the device on EMUI 4 Marshmallow rooted it and unlocked the bootloader then installed the BLN-L21C185B140 which worked smoothly.
I used that update.zip and extracted into dload root folder and started the huawei recovery installer but it said "package not found".
I tried flashing something to vendor before with fastboot but it said command not allowed.
Maybe I am doing something wrong?
Click to expand...
Click to collapse
Latest build on Nougat after the update was BLN-L22C185B140 so? If yes, the package that you need to download is that one. Unluckily i can't help about dload method, i never had fortune using dload because package verification always failed at 5%, i tried every combination but without success.
Command not allowed while flashing vendor image... but flashing others, like recovery or boot.img is allowed? If yes, i don't know what's causing this sorry... I'm sure that my friend @shashank1320 could surely help more than me about how using dload method correctly. Check his signature, it should contain a guide on how to use it

RedSkull23 said:
Latest build on Nougat after the update was BLN-L22C185B140 so? If yes, the package that you need to download is that one. Unluckily i can't help about dload method, i never had fortune using dload, i never be able to using it successfully because package verification always failed at 5%.
Command not allowed while flashing vendor image... but flashing others, like recovery or boot.img is allowed? If yes, i don't know what's causing this sorry... I'm sure that my friend @shashank1320 could surely help more than me about how using dload method correctly. Check his signature, it should contain a guide on how to use it
Click to expand...
Click to collapse
For fastboot yes flashing recovery or boot do work but vendor does not. Maybe the ISO is corrupted somehow I will try it again on a different machine now with the tool.
The link you posted the dload method from is the one where I initially found it as well so yea.
Also it shouldn't matter what I install since the only thing I need is the actual vendor (and product?) partition to work. I have a functional backup just TWRP cannot create/mount the partitions. So even a way to just create them without any data would actually fix my problem (at least I hope so?)

When trying to use Fastboot to flash the vendor/product img I get remote: Command not allowed (yes my bootloader is unlocked) although I can flash the recovery without any problem.
The dload method does not work as said. I placed the extracted content of the update.zip into the dload folder but the software "cannot find" the package.

algg said:
When trying to use Fastboot to flash the vendor/product img I get remote: Command not allowed (yes my bootloader is unlocked) although I can flash the recovery without any problem.
The dload method does not work as said. I placed the extracted content of the update.zip into the dload folder but the software "cannot find" the package.
Click to expand...
Click to collapse
@RedSkull23, thanks for the tag mate.
 @algg, No need to flash the vendor image as you already had the stock vendor img.
Now what else you can try is to flash the stock recovery, boot to stock recovery, select factory reset and reboot. It should most probably fix the issue.
If not, reflash the TWRP, a regular TWRO available and not specific to elite or meticulous, but generic one given by OldDroid.
I hope you have downloaded the content for dload, if not, download these for B140.
Flash this via TWRP- http://update.hicloud.com:8180/TDS/...afnaf/update_data_full_BLN-L21_hw_meafnaf.zip
no further changes and Then use dload method for this file- http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1756/g1755/v105054/f1/full/update.zip
Try above and provide feedback. This is what I could think of best possible way to have everything with all system app working.
If not, let me know and I will try to help further.

Hi, I thought I need the vendor image since TWRP (all versions) tell me "Could not mount/wipe vendor" and "Could not mount/wipe product" "invalid argument" for both.
I tried the factory reset before but it does not work. It stops at 23% then shows a red exclamation mark and just goes to the original screen with the 3 buttons (restart, shutdown and wipe).
I am currently trying to get it to recognize my sd card. But somehow it does not work through TWRP it just does not recognize the 8GB SD Card. Also I am currently on the TWRP I was before all of this happened (3.1 openkirin). Without the SD Card recognized I can't put the dload files for it on it and in turn I can't use the dload.
I mean technically it should very well be possible to fix the device since it isn't a real brick and even TWRP and Fastboot load. It's just that all those little things are somehow ruining it.

Edit: I will get a new micro sd for some reason this one does nt work. I'll say then whether the flash then dload worked.
@shashank1320
Mind explaining why I should first use TWRP to flash something and then on top of it use dload?
And why those specific files?

algg said:
Edit: I will get a new micro sd for some reason this one does nt work. I'll say then whether the flash then dload worked.
@shashank1320
Mind explaining why I should first use TWRP to flash something and then on top of it use dload?
And why those specific files?
Click to expand...
Click to collapse
Sure, let me explain.
The first file is the data file which will install few systems apps like file manager, updater, themes, clock, fm radio etc. This will work via dload as well but the installation time is around 3-7 seconds so, over the course of time and flashing few times, i realised that these PV files cannbe flashed via TWRP and it works perfectly fine specific to PV files( twrp won't supoort other stock zips). We foash this first so that it updates your buld number and also does not replace the recovery with stock (as if you flash the main update zip first, it will replace with stock recovery so flashing the 2nd file will be quick but with unstable system apps, sometime).
Now we flash the main zip file with update.app via dload and it Install the main firmware for boot, vendor, recovery, system, usrdata etc.
Hope this explanation helps, if not let me know and I will rephrase myself.

It does help. I did all of this and now in the dload app I get "Software install failed Incompatibilty with current version please download the correct update package".
When I flashed the zip you linked me with TWRP it said "cannot mount /data /vendor /product". Appearently data cannot be mounted since it is encrypted.
Any clue as to what I am doing wrong? Or is this device now a real brick with functioning recovery but without OS?

Is there any way I can "debug" what is going on while the boot animation is playing?
What is confusing me is that the boot animation plays just normal but it simply does not continue to the actual OS.

algg said:
It does help. I did all of this and now in the dload app I get "Software install failed Incompatibilty with current version please download the correct update package".
When I flashed the zip you linked me with TWRP it said "cannot mount /data /vendor /product". Appearently data cannot be mounted since it is encrypted.
Any clue as to what I am doing wrong? Or is this device now a real brick with functioning recovery but without OS?
Click to expand...
Click to collapse
Not bricked..its just Data is not mounted or encryption. Should never encrypted it. NVM.
Do one thing, boot to twrp recovery. Try flashing and get error, then go to main TWRP page and click on reboot, select recovery out of 4 options( power off, system, bootloader and recovery). It will boot to recovery, now try flashing it again and see. Most if the time it helps.
Else, go to main page, select wipe, click on format rather than wipe here, it will prompt for typing Yes to confirm. Biit to recovery from main twrp page ( as mentioned above). And try this same thing of formatting data couple of times and then flash the zip and then dload.
I know these are tedious steps but inhave revived my device many a times with all these tricks after some efforts.
Good luck

YAY it works.
Just to recap what I did:
I flashed your thing first through TWRP tried to flash your other link with dload (which did NOT work)
Then I flashed the thing (emui5 Android 7 for Europe) through TWRP played in my old backup of exactly this through TWRP cleared dalvik & cache.
Then I waited 20 minutse and now it started.
Really thanks to all of you very nice people here. I would be very baffled if it wasnt able to repair the device since Fastboot and Recovery still work.
But Huaweis recovery is beyond terrible.

algg said:
YAY it works.
Just to recap what I did:
I flashed your thing first through TWRP tried to flash your other link with dload (which did NOT work)
Then I flashed the thing (emui5 Android 7 for Europe) through TWRP played in my old backup of exactly this through TWRP cleared dalvik & cache.
Then I waited 20 minutse and now it started.
Really thanks to all of you very nice people here. I would be very baffled if it wasnt able to repair the device since Fastboot and Recovery still work.
But Huaweis recovery is beyond terrible.
Click to expand...
Click to collapse
It is terrible indeed. Glad your phone working.
Thanks to @RedSkull23 for tagging, else I may have not responded as he was already involved and was helping as usual.:good:

algg said:
Really thanks to all of you very nice people here. I would be very baffled if it wasnt able to repair the device since Fastboot and Recovery still work.
But Huaweis recovery is beyond terrible.
Click to expand...
Click to collapse
I'm happy for you man, indeed it would be so bad, especially because you got this device 3 or 4 days ago if i didn't read bad, anyway what matters is that now it works. Are you able to restore the previous backup through TWRP now? (But before trying... Make a backup of your actual OS )
shashank1320 said:
It is terrible indeed. Glad your phone working.
Thanks to @RedSkull23 for tagging, else I may have not responded as he was already involved and was helping as usual.:good:
Click to expand...
Click to collapse
Are you joking man? I just tagged you for more help, but practically you helped him in everything, not me; I'm sure that you would noticed the thread and helped as always even without my tag, i just speeded up things for being helpful to algg.
algg, I'd like to apologize myself; i didn't vanished after tagging shashank, today i just was at work and obviously i was busy for help, but as i saw with pleasure he already helped you to restore your OS and that was the objective. Nice one, guys!

Guide How to root Android 8.0 Oreo Stock ROM on Galaxy S7 ( 100% Working )

Hi . i see too many peoples have problem on rooting Android 8.0 Oreo Stock Rom on Galaxy S7 ( edge ) and they cant get passed from the verification field error ! ok its bcuz they do only 1 step wrong , here i just wanna tell you all the steps 1 by 1 to help you make it work .
ok first , if you wanna have a Rooted stock Oreo Rom , you need to factory reset your device , so backup everything you need then follow the steps :
1- Download Odin 3.13.1 -------- TWRP 3.2.3 Recovery -------- Android 8.0 Oreo Stock Rom -------- Magisk v 17.1 -------- no-verity-opt-encrypt-6.0 .
Copy Magisk v17.1 and no-verity-opt files into your SD card , or you can copy them after you installed TWRP using mount !
2- Go to Odin , and flash the Stock Rom oreo , BUT before you start go to Options and deselect F. reset time and Auto reboot .
{
"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"
}
3- when the Rom flash is done . just hold Power + volume down + home buttons to restart the phone . keep holding the buttons to return Download mode again !
NOTE : you have to reboot to download mode again after flashing Stock Rom . bcuz odin wont install TWRP and will stop on waiting for connection if you do flash TWRP right after flashing rom without reboot ! just after flashing ROM , do a reboot with device buttons and keep holding them to go straight to download mode again . then you can flash TWRP .
4- now go to Odin again and now Flash the TWRP recovery . before you start go to options and deselect F .reset time and Auto reboot .
5- now hold Power + Volume down + Home buttons , when your device screen goes off , fast switch the buttons to Power + Volume up + home to boot into TWRP recovry .
6- now go to Wipe and select Format Data . it will ask you to type yes . type yes and continue . you do this to remove encryption on your phone memory .
NOTE : Just select Format data . DON'T select advanced wipe or swip to factory reset . you have to select Format data and it will ask you to type "yes" . do it and go on .
7- now go to reboot and reboot to TWRP recovery again ! ( you have to reboot to recovery bcuz you cant reach /DATA when you do Format data )
8- now go to install , and install Magisk and no-Verity-opt .
9- now restart your phone normaly and let it boot up and do the first boot settings .
10 - thats it , now you can see Magisk on your apps list and your Stock Rom is rooted .
NOTE : for the guys that already installed Stock oreo Rom , they dont need to flash Rom again , they can skip Step 2 and 3 !
just do all the steps 1 by 1 as i said and it will work 100% . some guys cant make it work bcuz : 1 - they dont do Format Data before installing Magisk and they get "cant mount /data error" and verification field pops up . 2- they do format data after installing magisk !!!! thats crazy bcuz you just clear Magisk when you do format data after installing it .
i hope this guide be helpful for you guys .

does it work for sm g935s (8.0)

rama.91 said:
does it work for sm g935s (8.0)
Click to expand...
Click to collapse
yes , it works . you just need to download last version of TWRP recovery for your device from here :
https://twrp.me/Devices/Samsung/

Thx bro.

The root is fine but have problem with twrp failed to mount data invalid argument I followed the procedure several times

slavisa037 said:
The root is fine but have problem with twrp failed to mount data invalid argument I followed the procedure several times
Click to expand...
Click to collapse
Once you have to wipe data and restart to recovery again and then only install new Rom resolves data mount error.

Do thet but still error in twrp

Ist there any way to root without wipeing data?
Patching boot.img with Magisk dont work. I guess because of lz4...

Thank you, this is a great guide! Worth to mention that TWRP is flashed as AP in Odin, though.

Is this working for Galaxy S7 Edge SM-G935F ?

Hey hnegrao,
I've rooted my girlfriends Galaxy S7 Edge SM-G935F successfull with this instruction
@Arona67 thank you very much for sharing this instruction and your effort!
There's a question left: Can I remove Magisk and TWRP after successfully rooting?
I'd like to note that I've only needed the root permissions to change the build.prop file entry ro.config.tima=1 to 0; That S-Health works in spite of increased knox counter.
Best Regards

unfortunately I have a problem with this walkthrough. when I want to upload twrp I have the message: custom binary (recovery) blocked by frp lock. I have the newest soft.

hnegrao said:
Is this working for Galaxy S7 Edge SM-G935F ?
Click to expand...
Click to collapse
Same question

insert.smile said:
Same question
Click to expand...
Click to collapse
Yes,it works like a charm.
Just follow all the steps and you will be fine.

Hi. Many thanks for this.
I have to recover some data from my phone and for that I need root.
My question is, if I install TWRP, Format data, and then install Magisk, will it format the internal SD card? I mean will I still be able to recover those files or will they be gone? If they will be gone, it defeats the purpose of me rooting the phone.
EDIT: I have a G930W8 (Exynos)

mayanks_098 said:
Hi. Many thanks for this.
I have to recover some data from my phone and for that I need root.
My question is, if I install TWRP, Format data, and then install Magisk, will it format the internal SD card? I mean will I still be able to recover those files or will they be gone? If they will be gone, it defeats the purpose of me rooting the phone.
EDIT: I have a G930W8 (Exynos)
Click to expand...
Click to collapse
You will lose everything once you format the internal sd, better think twice.

Great post, followed all the instructions and my s7 is now running android 8 fine. One issue I've had, when I try to encrypt the device from the Samsung settings it starts the process off reboots twice and then comes back with a failure message whereby you have to fully reset the phone again as per instructions at top of post. Any way to get encryption to work on this?
Thanks all

Same process does NOT work on the latest Oreo update.
Flashed rom
Flashed twrp
Formatted data
Rebooted to recovery
Installed no-verity-opt-encrypt-6.0.zip
Installed Magisk 17.3 (same result even if Magisk is skipped, tried w/o due to this issue)
Rebooted to system and letting it boot up
Rebooting straight to recovery, and still get unable to mount data due to encryption.
Something in the latest stock kernel seem to be circumventing the no-verity-opt-encrypt zip since it was working on the previous update.
EDIT: Got it working by following this post and using the remove-encryption.zip found in that thread (this post).
Still no idea why no-verity-opt-encrypt-6.0.zip didn't work even without Magisk.

Does it work on S7 Edge 9350 stock ROM (Snapdragon) ?

What is the purpose of flashing o-verity-opt-encrypt-6.0 ? Can someone please clarify. ?

Ultimate guide to install stable or Dev rom from Xiaomi.eu

Hello everyone,
First of all, rom and recovery are not from me... I just want to make a full guide to help you
So let's go !!!!!
1 step: unlock bootloader
https://en.miui.com/unlock/
BE CAREFUL unlocking your bootloader will erase all your data (internal storage) so don't forget to make a backup
2 step: flash twrp recovery
Download the recovery image from here
https://drive.google.com/file/d/1-1CSfT4lQwFZngu6RI9eowLA9CmEMEPw/view?usp=drivesdk
Be sure to have adb and fastboot tools on your computer ... If not take a look at here
https://forum.xda-developers.com/showthread.php?t=2317790
Past TWRP_umi.img on minimal adb and fastboot directory.
Open a cmd here.
Enable usb debugging on your device
Reboot your phone on bootloader (hold volume down + power), connect it to PC and tape:
fastboot devices
fastboot flash recovery TWRP_umi.img
Then tape fastboot reboot while holding volume up button on your devices to reboot in recovery
3 step:
At the first launch of Twrp You have to choose SWIPE TO ALLOW MODIFICATION
4 step:
THIS ONE OF THE MUST IMPORTANT STEP
In twrp menu you have to go in Wipe data on choose format data
Otherwise the ROM will not boot.
5 step:
Reboot into recovery from twrp.
6 step:
Connect your phone to your PC and paste the xiaomi.eu ROM of your choice (stable or Dev)
7 step:
Flash ROM from recovery
8 step:
REBOOT AND ENJOY :good::good::good:

Does Xiaomi EU Rom run either on encrypted and unencrypted storage?

I cant get this to work, ive been trying everything for hours. I am sure i am missing something stupid but if anyone has any new ideas please let me know. I unlocked my device today, flashed twrp via fastboot, rebooted to recovery, formatted data then went on to install xiaomi eu rom. Ever since trying this, i am constantly booting into recovery or hitting a boot loop. i have formatted data more times than i care to think of ha ha. ive tried flashing the latest fastboot rom via mi unlock tool to do a fresh start but keep getting ''flash crclist error". Ive also tried flashing miui stock via twrp and it also, doesn't boot. ive tried many combinations in between. My next option is to try the fastboot global rom (though i believe i have a chinese device), i am waiting for it to download. If anyone knows what i am doing wrong i will be eternally grateful if you can tell me what it is. I'm so frustrated, been flashing roms for years, never had anything take as long as this :crying:

carolef1984 said:
I cant get this to work, ive been trying everything for hours. I am sure i am missing something stupid but if anyone has any new ideas please let me know. I unlocked my device today, flashed twrp via fastboot, rebooted to recovery, formatted data then went on to install xiaomi eu rom. Ever since trying this, i am constantly booting into recovery or hitting a boot loop. i have formatted data more times than i care to think of ha ha. ive tried flashing the latest fastboot rom via mi unlock tool to do a fresh start but keep getting ''flash crclist error". Ive also tried flashing miui stock via twrp and it also, doesn't boot. ive tried many combinations in between. My next option is to try the fastboot global rom (though i believe i have a chinese device), i am waiting for it to download. If anyone knows what i am doing wrong i will be eternally grateful if you can tell me what it is. I'm so frustrated, been flashing roms for years, never had anything take as long as this :crying:
Click to expand...
Click to collapse
try rhis
format data (not wipe)
put rom.zip unto ur internal storage
wipe cache an dalvik cache
now flash the zip
now reboot to recovery
wipe cache an dalvik cache
an now go to reboot menu
an now power off
an now power it on

-fluffy- said:
try rhis
format data (not wipe)
put rom.zip unto ur internal storage
wipe cache an dalvik cache
now flash the zip
now reboot to recovery
wipe cache an dalvik cache
an now go to reboot menu
an now power off
an now power it on
Click to expand...
Click to collapse
Thank you for trying to help, unfortunately it just rebooting to my recovery still. I dont suppose anyone has any other ideas do they please I cant understand what on earth ive done wrong. Does anyone know why mi flash tool comes up with that error (flash crc list error)? qualcomm drivers are installed.

carolef1984 said:
Thank you for trying to help, unfortunately it just rebooting to my recovery still. I dont suppose anyone has any other ideas do they please I cant understand what on earth ive done wrong. Does anyone know why mi flash tool comes up with that error (flash crc list error)? qualcomm drivers are installed.
Click to expand...
Click to collapse
write what u do wen u try to flash the zip
an have u downloadet the correct zip file

Thanks everyone, i think it must have been something to do with the qualcomm drivers installed incorrectly. i have re-done that from scratch and managed to get mi flash tool working. Sorry to waste everyones time.

Greetings
I have followed the tutorials to perfection like 2-3 times and I still face the same issue
I always go back to TWRP after trying to boot into system.
I have tried 2 different recovery files
The experimental one asks for a password. and the other one works but keeps going back to recovery after flashing.
MIUI 11 rom
MIUI 12 rom
No matter what I do It keeps going back to recovery.
It's my only device so I truly need help.
I have tried re installing everything already.
At this point I just want to install stock rom and keep using it without flashing anything please help.
PHONE FINALLY REBOOTING INTO SYSTEM. I myself don't know what i did!!!

Bootloop (stuck on 5G logo) after flashing Xiaomi.eu ROM
Dear fellow XDA-dev community members,
Xiaomi Mi 10 (umi), coming from original stock ROM, MIUI 11 GLOBAL version V11.0.2.0.QJBMIXM.
Bootloader unlocked official way via MiFlash Unlock 4.5.514.47.
Custom recovery TWRP 3.4.1b-0313 installed via XiaoMiTool V2.
Tested root by installing Magisk 20.3 via TWRP, no problem, then updating to Magisk 20.4 with the Magisk Manager 7.5.1.
The problems started when I tried to install Xiaomi.eu Custom ROM : xiaomi.eu_multi_MI10_V11.0.25.0.QJBCNXM_v11-10
Downloaded the Xiaomi.eu ROM to PC, then copied to the Download folder of the Phone.
Started phone in upload mode or TWRP. > Wipe > Swipe to Factory Reset + Format Data.
When formatting data I erase all folders in the phone, including the Xiaomi.eu ROM copied in the Download folder.
Some tutorials suggest to copy the Xiaomi.eu ROM from PC to phone after formatting the data, just by connecting the phone in TWRP to the PC, by going to > Mount and enabling MTP.
Tried this method but when I send the Xiaomi.eu ROM file to the phone the progress bas doesn’t move.
So I restarted the phone, without installing the Custom ROM, went through all the screens of initial phone configuration. Lost Magisk and root (but I supposed that it’s not mandatory to install Custom ROM). Copied again the Xiaomi.eu ROM zip file to the Download folder. Rebooted to TWRP. This time I just did Factory Reset but without Format Data. Then > Install to install the Xiaomi.eu new ROM. Cleared Dalvik Cache then reboot.
PROBLEM : bootloop. Stuck with the 5G logo forever, waited more than 30 min, no change.
Still have access to recovery TWRP and to bootloader mode. I suppose this is a soft brick?
I did > Wipe, Swipe to Factory Reset + Format Data, restarted… no change.
Copied this time the Xiaomi.eu ROM to a clean formatted (FAT32) USB drive. As shown in some tutorials, you can us an external USB drive via USB OTG to install the Custom ROM via TWRP.
Factory Reset + Format Data, then I installed again the same Xiaomi.eu ROM from the external USB. Still stuck in bootloop.
Please I need help to fix the problem
I’m not an expert developer, but I’m not a complete noob either.
This is the first time I have troubles with a brand new Xiaomi Phone.
It’s the first time I get a very expensive phone, but had no choice (they are getting very expensive), because I always buy a Flagship Xiaomi to get all the community support possible.
And I had to change the ROM to Xiaomi.eu, because the Official Global ROM is full of bloatware I had a good experience with Xiaomi.eu ROMs with my old Xiaomi Mi 4 and Mi 5.
At this point I don’t mind going back to stock MIUI Global ROM.
I suppose that with access to boot loader I can flash the Official ROM from PC with MiFlash2020-3-14-0? If it’s the case can somebody show me detailed steps to do that?
For Mi 10 Official Global there is the Stable Full ROM (miui_UMIGlobal_V11.0.2.0.QJBMIXM_4f986c08cb_10.0 ) (2.45 GB) and Stable ROM (umi_global_images_V11.0.2.0.QJBMIXM_20200328.0000.00_10.0_global_09b168ff9e) (3.76 GB). Which One to flash from PC with MiFlash?
I can’t afford to hard brick the device
Thank you very much.

andromomo said:
Dear fellow XDA-dev community members,
Xiaomi Mi 10 (umi), coming from original stock ROM, MIUI 11 GLOBAL version V11.0.2.0.QJBMIXM.
Bootloader unlocked official way via MiFlash Unlock 4.5.514.47.
Custom recovery TWRP 3.4.1b-0313 installed via XiaoMiTool V2.
Tested root by installing Magisk 20.3 via TWRP, no problem, then updating to Magisk 20.4 with the Magisk Manager 7.5.1.
The problems started when I tried to install Xiaomi.eu Custom ROM : xiaomi.eu_multi_MI10_V11.0.25.0.QJBCNXM_v11-10
Downloaded the Xiaomi.eu ROM to PC, then copied to the Download folder of the Phone.
Started phone in upload mode or TWRP. > Wipe > Swipe to Factory Reset + Format Data.
When formatting data I erase all folders in the phone, including the Xiaomi.eu ROM copied in the Download folder.
Some tutorials suggest to copy the Xiaomi.eu ROM from PC to phone after formatting the data, just by connecting the phone in TWRP to the PC, by going to > Mount and enabling MTP.
Tried this method but when I send the Xiaomi.eu ROM file to the phone the progress bas doesn’t move.
So I restarted the phone, without installing the Custom ROM, went through all the screens of initial phone configuration. Lost Magisk and root (but I supposed that it’s not mandatory to install Custom ROM). Copied again the Xiaomi.eu ROM zip file to the Download folder. Rebooted to TWRP. This time I just did Factory Reset but without Format Data. Then > Install to install the Xiaomi.eu new ROM. Cleared Dalvik Cache then reboot.
PROBLEM : bootloop. Stuck with the 5G logo forever, waited more than 30 min, no change.
Still have access to recovery TWRP and to bootloader mode. I suppose this is a soft brick?
I did > Wipe, Swipe to Factory Reset + Format Data, restarted… no change.
Copied this time the Xiaomi.eu ROM to a clean formatted (FAT32) USB drive. As shown in some tutorials, you can us an external USB drive via USB OTG to install the Custom ROM via TWRP.
Factory Reset + Format Data, then I installed again the same Xiaomi.eu ROM from the external USB. Still stuck in bootloop.
Please I need help to fix the problem
I’m not an expert developer, but I’m not a complete noob either.
This is the first time I have troubles with a brand new Xiaomi Phone.
It’s the first time I get a very expensive phone, but had no choice (they are getting very expensive), because I always buy a Flagship Xiaomi to get all the community support possible.
And I had to change the ROM to Xiaomi.eu, because the Official Global ROM is full of bloatware I had a good experience with Xiaomi.eu ROMs with my old Xiaomi Mi 4 and Mi 5.
At this point I don’t mind going back to stock MIUI Global ROM.
I suppose that with access to boot loader I can flash the Official ROM from PC with MiFlash2020-3-14-0? If it’s the case can somebody show me detailed steps to do that?
For Mi 10 Official Global there is the Stable Full ROM (miui_UMIGlobal_V11.0.2.0.QJBMIXM_4f986c08cb_10.0 ) (2.45 GB) and Stable ROM (umi_global_images_V11.0.2.0.QJBMIXM_20200328.0000.00_10.0_global_09b168ff9e) (3.76 GB). Which One to flash from PC with MiFlash?
I can’t afford to hard brick the device
Thank you very much.
Click to expand...
Click to collapse
try this
format data
reboot recovery
connect phone to pc
put zip file ro phone
wipe cache an dalvik cache
install zip
wipe again
reboot recovery
wipe again
go to reboot
power off the phone
now wen its shut down power it on
an it shut boot
it will take a litle time

andromomo said:
Dear fellow XDA-dev community members,
Xiaomi Mi 10 (umi), coming from original stock ROM, MIUI 11 GLOBAL version V11.0.2.0.QJBMIXM.
Bootloader unlocked official way via MiFlash Unlock 4.5.514.47.
Custom recovery TWRP 3.4.1b-0313 installed via XiaoMiTool V2.
Tested root by installing Magisk 20.3 via TWRP, no problem, then updating to Magisk 20.4 with the Magisk Manager 7.5.1.JBMIXM_4f986c08cb_10.0 ) (2.45 GB) and Stable ROM (umi_global_images_V11.0.2.0.QJBM
Thank you very much.
Click to expand...
Click to collapse
hi didt it work for u

IT WORKED properly like a charm!!!
Dear -fluffy-,
Thank you very much for your quick reply.
I followed precisely your instructions. I was able to copy de ROM zip file from PC to the phone (the transfer bas went smoothly, as opposite as before).
IT WORKED properly like a charm!!!
Booting the phone took me 2 min.
---------- Post added at 12:57 PM ---------- Previous post was at 12:47 PM ----------
Dear -fluffy-,
Thank you very much for your quick reply.
I followed precisely your instructions. I was able to copy de ROM zip file from PC to the phone (the transfer bas went smoothly, as opposite as before).
IT WORKED properly like a charm!!!
Booting the phone took me 2 min.
---------- Post added at 01:15 PM ---------- Previous post was at 12:57 PM ----------
I followed precisely your instructions. I was able to copy de ROM zip file from PC to the phone (the transfer bas went smoothly, as opposite as before).
IT WORKED properly like a charm!!!
Booting the phone took me 2 min.

Quick questions, do netflix and google pay work after the flash?

tott2003 said:
Quick questions, do netflix and google pay work after the flash?
Click to expand...
Click to collapse
yes

cedric3320 said:
4 step:
THIS ONE OF THE MUST IMPORTANT STEP
In twrp menu you have to go in Wipe data on choose format data
Click to expand...
Click to collapse
Hello,
i have a silly question about step 4:
someone says we should "Wipe Data", someone says we should "Format Data" ,
i don't see a real difference unless we want to change the filesystem type.
Advices ?
And also, when we format ( or wipe ) the "Data" partition, are we formatting the 256 GB partition ?
if yes, this is a really huge drawback for us who want to change ROM more frequently than other android users, because we have to backup a 256 GB partition ...
This is not fast to do online ( at least with my poor connection ) and it is not fast to do on PC or on a USB KEY.
So we have 256 GB and we need to format at each ROM change ? Too bad ...
In the good old times i did extract my microSD card and i was safe .
Someone could explain me please ?
thank you all for your patience...

adario73 said:
Hello,
i have a silly question about step 4:
someone says we should "Wipe Data", someone says we should "Format Data" ,
i don't see a real difference unless we want to change the filesystem type.
Advices ?
And also, when we format ( or wipe ) the "Data" partition, are we formatting the 256 GB partition ?
if yes, this is a really huge drawback for us who want to change ROM more frequently than other android users, because we have to backup a 256 GB partition ...
This is not fast to do online ( at least with my poor connection ) and it is not fast to do on PC or on a USB KEY.
So we have 256 GB and we need to format at each ROM change ? Too bad ...
In the good old times i did extract my microSD card and i was safe .
Someone could explain me please ?
thank you all for your patience...
Click to expand...
Click to collapse
Hello,
You have to format data the first time you flash xiaomi.eu rom because their rom is base on Chinese firmware (if you don't or just wipe it will not boot)
Each time you will flash a rom with different base (from Chinese base to global base or global to Chinese) you will have to format data !!

You format data to remove encryption.

tott2003 said:
Quick questions, do netflix and google pay work after the flash?
Click to expand...
Click to collapse
Google pay isn't working as the safety net doesn't pass on stable realeses, someone made it to work on betas but I had no luck though

Stuck without solutions
Hello,
I tried to flash the latest miui 12. I followed all the steps...
But now I can't acess recovery nor rom.
Basically when i try to flash TWRP with bootloader it just goes back to fastboot.
Also note that the flash is successful. But I somehow can't acess TWRP, just goes back to fastboot
And when I flash the experimental TWRP on the dev thread it boots to recovery but asks for a password.. Impossible to flash anything.. Even after I formated data and everything
I tried flashing other TWRP I found but nothing boots even after trying a lot of time.
I tried <fastboot boot recovery.img> as well
I tried <fastboot erase recovery> and then flash the TWRP as well
I've been trying hard for the last 8 hours.
I also have a backup of when I had MIUI 12. But impossible to flash it with the only recovery I can boot to.
I feel so desperate. I'm out of ideas.
If you have any ideas, I'm listening
Thanks for the help guys.

Dallee said:
Hello,
I tried to flash the latest miui 12. I followed all the steps...
But now I can't acess recovery nor rom.
Basically when i try to flash TWRP with bootloader it just goes back to fastboot.
Also note that the flash is successful. But I somehow can't acess TWRP, just goes back to fastboot
And when I flash the experimental TWRP on the dev thread it boots to recovery but asks for a password.. Impossible to flash anything.. Even after I formated data and everything
I tried flashing other TWRP I found but nothing boots even after trying a lot of time.
I tried <fastboot boot recovery.img> as well
I tried <fastboot erase recovery> and then flash the TWRP as well
I've been trying hard for the last 8 hours.
I also have a backup of when I had MIUI 12. But impossible to flash it with the only recovery I can boot to.
I feel so desperate. I'm out of ideas.
If you have any ideas, I'm listening
Thanks for the help guys.
Click to expand...
Click to collapse
an what is the latest miui12 u try to flash

[RECOVERY][UNOFFICIAL]TWRP Recovery Project 3.5.2 Micromax IN 1 (E6746)

{
"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 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface 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.
*/Your warranty is now void.
We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or recoverys, kernels.
You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers./*
Click to expand...
Click to collapse
FLASH GUIDE
1. Unlocked your bootloader
2. Download twrp-3.5.2-e6746.img
3. Run this Following commands
1. adb reboot bootloader
2. fastboot --disable--verification flash vbmeta vbmeta.img
3. fastboot flash recovery twrp-3.5.2-e6746.img
4. fastboot reboot recovery
Click to expand...
Click to collapse
DOWNLOAD
Device Tree
Working
• Decryption
• fastbootd
• MTP & ADB
Bugs
• spam me in support group
• Tell me
Support group
• here
Credits
• TEAM WIN FOR TWRP
• @ZanGhoul in TG
• and @uknowndevice in TG

where is vbmeta.img
I am trying to backup stock recovery using
fastboot boot <recoveryname>.img
says ok but boots to stock recovery not TWRP.

sieger007 said:
where is vbmeta.img
I am trying to backup stock recovery using
fastboot boot <recoveryname>.img
says ok but boots to stock recovery not TWRP.
Click to expand...
Click to collapse
Much better fastboot flash twrp.img, but if you backup stock recovery, just try to pull it via adb

ok I dont have root. How can I backup recovery and other partitons without root

sieger007 said:
ok I dont have root. How can I backup recovery and other partitons without root
Click to expand...
Click to collapse
Try, reboot to recovery mode if, pc read your device adb pull /dev/block/by-name/recovery

mastersenpai05 said:
Try, reboot to recovery mode if, pc read your device adb pull /dev/block/by-name/recovery
Click to expand...
Click to collapse
that is the problem
fastboot boot recovery does not boot to TWRP & I dont have root - I am stuck

if I could temporarily install any custom recovery - problem is solved - Nandroid backup and adb pull. Problem is it keeps going back to stock recovery & i dont want to flash TWRP unless I back up stock recovery. Any thoughts ?

sieger007 said:
if I could temporarily install any custom recovery - problem is solved - Nandroid backup and adb pull. Problem is it keeps going back to stock recovery & i dont want to flash TWRP unless I back up stock recovery. Any thoughts ?
Click to expand...
Click to collapse
Yeah, stock rom issue need to root sir, but I will fix it sir.

sieger007 said:
if I could temporarily install any custom recovery - problem is solved - Nandroid backup and adb pull. Problem is it keeps going back to stock recovery & i dont want to flash TWRP unless I back up stock recovery. Any thoughts ?
Click to expand...
Click to collapse
Not in stock firmware sir? The stoc recovery.img?

mastersenpai05 said:
Not in stock firmware sir? The stoc recovery.img?
Click to expand...
Click to collapse
I meant I tried .... fastboot boot <thisTWRPfile>.img after running vmeta and it will still boot into stock recovery. If I boot in stock recovery - adb shell will not run cos stock recovery does not support it. Problem is there isnt so far stock firmware available , so if I mess up and no backup - I have to run to service center and more $

sieger007 said:
I meant I tried .... fastboot boot <thisTWRPfile>.img after running vmeta and it will still boot into stock recovery. If I boot in stock recovery - adb shell will not run cos stock recovery does not support it. Problem is there isnt so far stock firmware available , so if I mess up and no backup - I have to run to service center and more $
Click to expand...
Click to collapse
MICROMAX IN 1 E6746 http://mtk-p.micromaxinfo.com/product/E6746/Software/India/MMX_E6746_SW_V10.0._HW_V1.0_20210416.zip

mastersenpai05 said:
MICROMAX IN 1 E6746 http://mtk-p.micromaxinfo.com/product/E6746/Software/India/MMX_E6746_SW_V10.0._HW_V1.0_20210416.zip
Click to expand...
Click to collapse
thanks i will check it out. Just wanted to check if this TWRP support USB OTG.Want to transfer Nandroid backup to FLash Drive

sieger007 said:
thanks i will check it out. Just wanted to check if this TWRP support USB OTG.Want to transfer Nandroid backup to FLash Drive
Click to expand...
Click to collapse
Yes sir, I want to know that too. Not yet try but try to check then tell me

TWRP installed fine . OTG works. Now the other 3 letter problem .....OTA.
I got notification that update is available. It wont install via TWRP.
How do I install OTA. wrt THis guide .... this phone does not seem to fit ( this isn't A/B phone type A phone ) . WHat do I do ? restore stock recovery and boot and then restore TWRP and boot.patch.img ? Any clue ?

sieger007 said:
TWRP installed fine . OTG works. Now the other 3 letter problem .....OTA.
I got notification that update is available. It wont install via TWRP.
How do I install OTA. wrt THis guide .... this phone does not seem to fit ( this isn't A/B phone type A phone ) . WHat do I do ? restore stock recovery and boot and then restore TWRP and boot.patch.img ? Any clue ?
Click to expand...
Click to collapse
I don't think so if possible to use twrp in ota update, but you can use twrp for flashing recovery rom ( stock recovery rom)

mastersenpai05 said:
I don't think so if possible to use twrp in ota update, but you can use twrp for flashing recovery rom ( stock recovery rom)
Click to expand...
Click to collapse
I don't know what are the exact criteria for successful OTA update from a vague idea I think it check whether there is original boot and recovery image otherwise says no
in that case would flashing this DM verify no encrypt module remove this checking and after installing this we should be able to to install periodic OTA updates
or as a long-term procedure every time I have to install OTA I have to restore original boot and recovery or should I just restore recovery

as follow up - I could install OTA by restoring stock r'y . There isn't a need to restore boot. You can keep it this way or else if TWRP is restored the same proc ought to repeat before the next OTA.
I am attaching stock boot and recoveries here in case they could be of use.
Boot-recovery--mmx1

sieger007 said:
as follow up - I could install OTA by restoring stock r'y . There isn't a need to restore boot. You can keep it this way or else if TWRP is restored the same proc ought to repeat before the next OTA.
I am attaching stock boot and recoveries here in case they could be of use.
Boot-recovery--mmx1
Click to expand...
Click to collapse
Nice thank you so much! You can also join in micromax in 1 group in telegram

Update : it never worked. I thought it did but that update notice sprung and it wanted to do it all over again. I restored stock recovery. No Luck OTA's keep failing. I then restored stock Boot after removing magisk . Still got veriification error. My BL is unlocked. What does it take to get my OTA zip file working.... do I flash dm verify force encrypt . Why does it refuse. Should BL be locked as well anyone have luck push OTA update after rooting IN 1

Do you have kernel source code