Develop Bugs

How to Root Desire EYE [Simple Guide]

Rooting your device may cause loss of warranty.
1. Check your device model - This guide is for HTC Desire Eye and its variants including AT&T Model and International Unlocked Model only.
2. Backup - Backup is mandatory since bootloader unlock will erase your device to factory.
Requirentments- First you should have bootloader unlocked device. (Please visit "http://www.htcdev.com/bootloader" to unlock your bootloader)
Installed ADB Drivers and files - tool can found here, link - https://drive.google.com/file/d/0B9SWmcUAdoOnOVpITTVtcFZUZUk/view?usp=sharing
Download your recovery.img here, link - https://drive.google.com/file/d/0B9SWmcUAdoOnc3hOLXpWVVFIc2c/view?usp=sharing
Super SU & binary here, link - http://download.chainfire.eu/593/SuperSU/BETA-SuperSU-v2.19.zip?retrieve_file=1
Put recovery.img to your ADB folder in PC, and super su to your mobile.
3. Now start command line in the ADB folder where your files located in the PC (Right click + hold down Shift) then "Open command window here"
Guide - http://www.tech-recipes.com/rx/232/right-click-to-open-a-command-prompt/
4. Run following commands to flash recovery.img to your device ( this will replace your original recovery)
fastboot flash recovery recovery.img
Simple.. Now reboot into recovery by pressing power+vol down, then select recovery in the loading screen (if you have any issues rebooting into loader screen please try after disable quick boot in power settings).
5. Now flash your Super SU (Zip) transferred to your mobile by selecting in the recovery.
Everything good to go after reboot.....!!!!

I flashed the recovery image and it keeps coming up with a little screen with a red triangle,any ideas? thanks

pimpsuprazx said:
I flashed the recovery image and it keeps coming up with a little screen with a red triangle,any ideas? thanks
Click to expand...
Click to collapse
Bootloader unlocked?

Can you post a screenshot (PIC) ?

That what happened after flashing the recovery.img and booting into recovery:
{
"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"
}

johnyboo said:
That what happened after flashing the recovery.img and booting into recovery:
Click to expand...
Click to collapse
Same problem here.. Really sad.. Was the recovery image working???

jolishj said:
Same problem here.. Really sad.. Was the recovery image working???
Click to expand...
Click to collapse
Odd that there a few having problems. I s-off'd and had this recovery installed very easily. Are you all still having problems?

unforseenenemy said:
Odd that there a few having problems. I s-off'd and had this recovery installed very easily. Are you all still having problems?
Click to expand...
Click to collapse
the same issue here
like the recovery is not compatible

Try using the recovery found here: http://forum.xda-developers.com/desire-eye/development/recovery-twrp-2-8-4-0-htc-desire-eye-t3008442

I have rooted my phone, But when I uninstall any system app using system app remover after restarting app will be back, and I can't uninstall them.
What's the problem??

karo222 said:
I have rooted my phone, But when I uninstall any system app using system app remover after restarting app will be back, and I can't uninstall them.
What's the problem??
Click to expand...
Click to collapse
System write protection.
There is a mod to disable that here: http://forum.xda-developers.com/des...e-disable-write-protection-v1-0-tool-t2966850
Or use a custom ROM, those have it disabled already.

I went through all the necessary steps. Only thing/issue now is the actual flashing of the root file. It will not take. Anyone else have this issue? Is there a way to get the necessary binary or whatever it's asking for? Thank you in advance.
-Carlos

I have exactly the same issue

hondalude89 said:
I went through all the necessary steps. Only thing/issue now is the actual flashing of the root file. It will not take. Anyone else have this issue? Is there a way to get the necessary binary or whatever it's asking for? Thank you in advance.
-Carlos
Click to expand...
Click to collapse
Only you have to Download BETA-SuperSU-v2.71-20160331103524.zip and flash it. Issue Solved

I did all the steps and everythign went fine, but then I downloaded a RootChecker app and it says I dont have root access. How can I make sure everything worked? NVM I GOT IT FIXED THANX ALOT FOR THIS POST!!!

Shameera_N said:
Rooting your device may cause loss of warranty.
1. Check your device model - This guide is for HTC Desire Eye and its variants including AT&T Model and International Unlocked Model only.
2. Backup - Backup is mandatory since bootloader unlock will erase your device to factory.
Requirentments- First you should have bootloader unlocked device. (Please visit "http://www.htcdev.com/bootloader" to unlock your bootloader)
Installed ADB Drivers and files - tool can found here, link - https://drive.google.com/file/d/0B9SWmcUAdoOnOVpITTVtcFZUZUk/view?usp=sharing
Download your recovery.img here, link - https://drive.google.com/file/d/0B9SWmcUAdoOnc3hOLXpWVVFIc2c/view?usp=sharing
Super SU & binary here, link - http://download.chainfire.eu/593/SuperSU/BETA-SuperSU-v2.19.zip?retrieve_file=1
Put recovery.img to your ADB folder in PC, and super su to your mobile.
3. Now start command line in the ADB folder where your files located in the PC (Right click + hold down Shift) then "Open command window here"
Guide - http://www.tech-recipes.com/rx/232/right-click-to-open-a-command-prompt/
4. Run following commands to flash recovery.img to your device ( this will replace your original recovery)
fastboot flash recovery recovery.img
Simple.. Now reboot into recovery by pressing power+vol down, then select recovery in the loading screen (if you have any issues rebooting into loader screen please try after disable quick boot in power settings).
5. Now flash your Super SU (Zip) transferred to your mobile by selecting in the recovery.
Everything good to go after reboot.....!!!!
Click to expand...
Click to collapse
It is not working on my HTC DESIRE EYE
Error: The code execution cannot proceed because RAPI.DLL was not found.
Troubleshooting steps:
1. Make sure the downloaded file is unzipped
2. USB Debugging enabled
3. On my phone i selected the option, USE USB FOR: "usb file transfer"
4. On my phone I also tried selecting the option, USE USB FOR: "CD Installer"
5. Restart Phone, Mobile and the downloaded file

BlackView BV9600 Pro + LineageOS?

Hi! Could you please explain if this ROM will be compatible with my smartphone? I'm not sure, I don't found it on the list on LineageOS website.

Well, someone need to compile it for our bv9600 - i also would appreciate it, but i don't have thoose skills...

Also, lenovo vibe c2

i am not even not able to root my device (blackview bv9600 pro) i don't think that you will be able to have any lineage rom also...
have anyone success to root this device?

giannhs_n said:
i am not even not able to root my device (blackview bv9600 pro) i don't think that you will be able to have any lineage rom also...
have anyone success to root this device?
Click to expand...
Click to collapse
jup, runs root - magisk

AMDFenics said:
jup, runs root - magisk
Click to expand...
Click to collapse
can you explain how did you get root? or give me a guide, all the internet guides i tried failed!
thanks

giannhs_n said:
can you explain how did you get root? or give me a guide, all the internet guides i tried failed!
thanks
Click to expand...
Click to collapse
simply follow this guide -> LINK
- allow OEM unlock in the dev-settings (hit 5 times build number to see)
- allow usb debugging
- reboot to fastboot
- send "fastboot devices" command
- send "fastboot oem unlock" -> acknowledge
- send "fastboot flashing unlock" -> acknowledge
- flash the twrp image "fastboot flash recovery name_of_the_image.img"
- reboot into twrp by power of the device
- after that press vol+ up and power button (if i remember correct.. ) to get into twrp
- now u need a sd-card (micro) put no verity opt encrypt on it and magisk
- Backup all partitions u find.
- format data partition to get the size
- install magisk
- install no verity opt...
reboot
BV9600 should be rooted. Took me serveral times to get it working, because u need directly after "Flashing unlock command" to get the twrp stuff done.
Credits
The TWRP.img comes from www.unofficialtwrp.com
The encryption disabler comes from @Zackptg5 all credits to him. THANKS -> his site LINK
Enjoy

AMDFenics said:
simply follow this guide -> LINK
- allow OEM unlock in the dev-settings (hit 5 times build number to see)
- allow usb debugging
- reboot to fastboot
- send "fastboot devices" command
- send "fastboot oem unlock" -> acknowledge
- send "fastboot flashing unlock" -> acknowledge
- flash the twrp image "fastboot flash recovery name_of_the_image.img"
- reboot into twrp by power of the device
- after that press vol+ up and power button (if i remember correct.. ) to get into twrp
- now u need a sd-card (micro) put no verity opt encrypt on it and magisk
- Backup all partitions u find.
- format data partition to get the size
- install magisk
- install no verity opt...
reboot
BV9600 should be rooted. Took me serveral times to get it working, because u need directly after "Flashing unlock command" to get the twrp stuff done.
Credits
The TWRP.img comes from www.unofficialtwrp.com
The encryption disabler comes from @Zackptg5 all credits to him. THANKS -> his site LINK
Enjoy
Click to expand...
Click to collapse
thanks for the detailed information,
can you also tell me your frimewire version also because i am not available to boot on recovery!
{
"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"
}

giannhs_n said:
thanks for the detailed information,
can you also tell me your frimewire version also because i am not available to boot on recovery!
View attachment 4705498
Click to expand...
Click to collapse
exact same version.
---------- Post added at 10:29 PM ---------- Previous post was at 10:27 PM ----------
First u need to go to fastboot mode, to unlock "OEM UNLOCK"
This is easy via adb
-> reboot fastboot
Did u install the correct driver? (ADB driver) is ur device listed?

i tried repacking it myself but with no luck so far, also tried various treble GSI, all booting on my BV9600Pro and basically working but mobile data and phone are broken so that's not an option for now

I don’t understand why unblock the bootloader at all if everything is installed on the MTK platform using the SP Flash Tool !?
Why these dances with adb and fastboot? if a everything is done much easier ...
You do not install the factory software using adb ? not ?? so why can't TWRP be installed and installed using the SP Flash Tool!? Why complicate things?

Root with sp Flash tool
Hi please Anyone could explain this procedure with Sp Flash Tool and post it?

serg2327 said:
I don’t understand why unblock the bootloader at all if everything is installed on the MTK platform using the SP Flash Tool !?
Why these dances with adb and fastboot? if a everything is done much easier ...
You do not install the factory software using adb ? not ?? so why can't TWRP be installed and installed using the SP Flash Tool!? Why complicate things?
Click to expand...
Click to collapse
Because the vendor (Blackview) locks the bootloader (like any other brand does) and does not allow installing any other recovery without it.!?

AMDFenics said:
Because the vendor (Blackview) locks the bootloader (like any other brand does) and does not allow installing any other recovery without it.!?
Click to expand...
Click to collapse
Is this a statement or a question? Sorry, I do not know English and I use a translator ..
II repeat once again, in order to install TWRP you do not need to unlock the bootloader!
it installs without problems using the SP Flash Tool
and this is not an assumption but a statement!
My first copy of the smartphone received TWRP. It was on my copy that all the first tests of TWRP and ROOT were conducted.

serg2327 said:
Is this a statement or a question? Sorry, I do not know English and I use a translator ..
II repeat once again, in order to install TWRP you do not need to unlock the bootloader!
it installs without problems using the SP Flash Tool
and this is not an assumption but a statement!
My first copy of the smartphone received TWRP. It was on my copy that all the first tests of TWRP and ROOT were conducted.
Click to expand...
Click to collapse
I'm glad to hear that it works that way to you. But that doesn't worked for me. So i wrote the way i took, to root. Let the others choose, wich way works for them. :fingers-crossed::good:

I am using another MTK device and SP FlashTool is great it lets you recover from any software brick. So I will advice people to use this method.
I am planning on buying bv9600 pro and having twrp ported and root is a good start to custom roms.
The touch driver issue on twrp should be easily solved with the good kernel module for the twrp. And official twrp support would be nice.
Subscribed to the thread will see where it goes.

hi guys, can you share a clean system twrp backup of bv9600? because my USB is damaged and i can not use sp flash tool to clean restore. thanks!

Hi, i try to root my bv9600 pro, but all i end up is on reboot the system restores to factory no TWRP or anything on it. I connected it to MTKdroidtools and it complains about a file /system/recovery-from-boot.p which restores recovery and obviously after it the system too.
Thanks for any help
edit: LOL nevermind, working fine now, don't know what was going wrong, in a last try just downloaded the latest stable magisk again. Thanks AMDFenics for the howto
Just one thing, can i get rid of this 5 sec. warning that the mobile is unlocked?

dark-wulf said:
Hi, i try to root my bv9600 pro, but all i end up is on reboot the system restores to factory no TWRP or anything on it. I connected it to MTKdroidtools and it complains about a file /system/recovery-from-boot.p which restores recovery and obviously after it the system too.
Thanks for any help
edit: LOL nevermind, working fine now, don't know what was going wrong, in a last try just downloaded the latest stable magisk again. Thanks AMDFenics for the howto
Just one thing, can i get rid of this 5 sec. warning that the mobile is unlocked?
Click to expand...
Click to collapse
Maybe there is a way, but i don't know him. It is a common way for many manufacturer, to say, "here u did something you are not supposed too"

https://www.mediafire.com/file/0j0bx6cb0cb58f5/BV9600Pro_30042019_full.zip/file
Latest Firmware (04.2019) Clean SP Flash tool Backup

adb/twrp issues....

Firstly, when plugging my 7t in to my windows 10 PC, I am asked to choose which mode to go in within usb preferences, as I did previously in order to achieve and ADB driver connection I chose file transfer.......
this didn't work for some reason, only when in MIDI did I get a confirmation with adb devices.....even though there is still no sign of adb interface in device manager.....
any ideas? I can get adb connection with MIDI but is this good enough to flash recoveries/boot images etc....?
I tried to flash twrp and I could successfully boot into twrp directly via fastboot but twrp couldn't seen any of my storage, despite having all security methods turned off...
all i want to do is gain root access but I am having no joy....
ever since android 10 rooting anything for me has been a pain in the ass......truly fed up....it shouldn't be this hard......
I also flashed a patched boot image in an attempt to gain root access but it all did was break my wifi........which i fixed by copying over the latest image and installing locally......
please HELP....

Everything about this issues is already said in this forum.

Try looking at this topic here:
https://forum.xda-developers.com/oneplus-7t/development/recovery-unofficial-twrp-recovery-t3976961

ontwykende said:
Try looking at this topic here:
https://forum.xda-developers.com/oneplus-7t/development/recovery-unofficial-twrp-recovery-t3976961
Click to expand...
Click to collapse
sweet, ill check it out.....

ontwykende said:
Try looking at this topic here:
https://forum.xda-developers.com/oneplus-7t/development/recovery-unofficial-twrp-recovery-t3976961
Click to expand...
Click to collapse
It would seem that TWRP is a no go, for awhile at least.....
anyone managed to gain root access by flashing a patched boot.img?

mediaman123 said:
It would seem that TWRP is a no go, for awhile at least.....
anyone managed to gain root access by flashing a patched boot.img?
Click to expand...
Click to collapse
Lots of people have. Just boot your version and use magisk to direct install and reboot then you have root

Josh McGrath said:
Lots of people have. Just boot your version and use magisk to direct install and reboot then you have root
Click to expand...
Click to collapse
Normally I would be able to carry out such tasks but because I now feel so fed up with it all could I trouble you to tell my step by step how that is done.....?
many thanks..

mediaman123 said:
Normally I would be able to carry out such tasks but because I now feel so fed up with it all could I trouble you to tell my step by step how that is done.....?
many thanks..
Click to expand...
Click to collapse
I made a tool to install the latest ADB, Fastboot and USB drivers for windows, its very easy to use, just double click the file to start the installation process
you can see it here:
https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445
Screenshot:
{
"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"
}

fawazahmed0 said:
I made a tool to install the latest ADB, Fastboot and USB drivers for windows, its very easy to use, just double click the file to start the installation process
you can see it here:
https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445
Screenshot:
Click to expand...
Click to collapse
I can operate that fine, its just how to obtain boot.img files etc, patch them and so on..

mediaman123 said:
I can operate that fine, its just how to obtain boot.img files etc, patch them and so on..
Click to expand...
Click to collapse
Oh, I thought, you are have issues with adb, and for root, you just have to flash magisk using twrp

fawazahmed0 said:
Oh, I thought, you are have issues with adb, and for root, you just have to flash magisk using twrp
Click to expand...
Click to collapse
This isn't functional at the minute as TWRP, whether its flashed or booted from, cant get past the encryption.......it cant see/mount the internal storage....

mediaman123 said:
This isn't functional at the minute as TWRP, whether its flashed or booted from, cant get past the encryption.......it cant see/mount the internal storage....
Click to expand...
Click to collapse
You will have to wipe the data and then twrp can access internal storage.
This is how I did (in my phone, which is not Oneplus, but the process remain same for all phones), boot to fastboot mode and type this:
fastboot -w
Now, boot your phone to recovery mode:
(Now take complete twrp backup of your phone, and save it in your pc, before proceeding futher)
flash DM verity disabler: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
flash magisk: https://github.com/topjohnwu/magisk_files/raw/canary/magisk-release.zip
Now boot the phone back to OS and you will have root access

fawazahmed0 said:
You will have to wipe the data and then twrp can access internal storage.
This is how I did (in my phone, which is not Oneplus, but the process remain same for all phones), boot to fastboot mode and type this:
fastboot -w
Now, boot your phone to recovery mode:
(Now take complete twrp backup of your phone, and save it in your pc, before proceeding futher)
flash DM verity disabler: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
flash magisk: https://github.com/topjohnwu/magisk_files/raw/canary/magisk-release.zip
Now boot the phone back to OS and you will have root access
Click to expand...
Click to collapse
thanks for this......want to try and avoid wiping if possible but if I really want root I will do it.....
what does the command fastboot -w do?

mediaman123 said:
thanks for this......want to try and avoid wiping if possible but if I really want root I will do it.....
what does the command fastboot -w do?
Click to expand...
Click to collapse
it wipe's the data

mediaman123 said:
This isn't functional at the minute as TWRP, whether its flashed or booted from, cant get past the encryption.......it cant see/mount the internal storage....
Click to expand...
Click to collapse
fawazahmed0 said:
You will have to wipe the data and then twrp can access internal storage.
This is how I did (in my phone, which is not Oneplus, but the process remain same for all phones), boot to fastboot mode and type this:
fastboot -w
Now, boot your phone to recovery mode:
(Now take complete twrp backup of your phone, and save it in your pc, before proceeding futher)
flash DM verity disabler: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
flash magisk: https://github.com/topjohnwu/magisk_files/raw/canary/magisk-release.zip
Now boot the phone back to OS and you will have root access
Click to expand...
Click to collapse
TWRP is not functional at the moment, so stay away from it.
The only way to root right now is to use the patch boot image method.

Lossyx said:
No don't do this.... This is not about encryption at all. It's about the major partitioning changes that has happened in Android 10. Wiping the system will just make everything worse.
Avoid using TWRP at all.
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Oh, I didn't know this phone was on Android 10, Thanks for letting me know.
TWRP doesn't support Android 10 yet.
You can see it here
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
Actually there is a twrp compiled for this phone, but that doesn't work , you can see the messages in thread:
https://forum.xda-developers.com/oneplus-7t/development/recovery-unofficial-twrp-recovery-t3976961
The steps I told, was for Android 9 and earlier devices, I assumed, this is an old device.
@mediaman123, So please wait, until twrp starts supporting the Android 10.
And for rooting, I am not sure, whether magisk supports this new phone or not.
Maybe @Lossyx can help you on that.

https://forum.xda-developers.com/oneplus-7t/how-to/guide-how-to-root-oneplus-7t-twrp-t3979307
Sent from my OnePlus7TPro using XDA Labs

Lossyx said:
https://forum.xda-developers.com/oneplus-7t/how-to/guide-how-to-root-oneplus-7t-twrp-t3979307
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Seen this, however my device, the European version, is running on 10.0.6.....
The only boot images available with that post is the 10.0.3...
wouldn't feel comfortable using them.....
I would like to know how to extract the stock boot image from either the firmware file or the phone itself...

mediaman123 said:
Seen this, however my device, the European version, is running on 10.0.6.....
The only boot images available with that post is the 10.0.3...
wouldn't feel comfortable using them.....
I would like to know how to extract the stock boot image from either the firmware file or the phone itself...
Click to expand...
Click to collapse
You can go ahead and just fastboot boot them. If it works then just proceed, if it doesn't, just hold volume up+down and power button. (To boot into fastboot or restart phone)
Nothing will change in the system because it only boots a temporary image.
If your want to extract your own boot image you can use this tool.
https://github.com/cyxx/extract_android_ota_payload
Sent from my OnePlus7TPro using XDA Labs

Lossyx said:
You can go ahead and just fastboot boot them. If it works then just proceed, if it doesn't, just hold volume up+down and power button. (To boot into fastboot or restart phone)
Nothing will change in the system because it only boots a temporary image.
If your want to extract your own boot image you can use this tool.
https://github.com/cyxx/extract_android_ota_payload
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
So if it boots an older image successfully I can move it over to the phone to patch to then flash it or use the already patched one and flash that...?..

[GUIDE/TIP]Failed fastboot flashing of stock ROM

I was on stock ROM (12.0.8.0 QJSEUXM) and noticed that v12.0.9.0 is out for some time already, but not offered by system to be installed. In the past with my previous phones when I wanted to "force" the update, I simply downloaded fastboot ROM, flashed it and re-rooted the phone. In a matter of few minutes I had up-to-date and working phone again. Today I tried the same with Mi 10T lite and it failed miserably.
Observed issues:
1. flashing script (flash_all_except_storage.bat) comes with CRCLIST and SPARECRCLIST commands which are either not understood by phone (fastbootd), or fail verification (fastboot)
2. after modification of script and removal of beforementioned lines, flashing completes, however phone stays in bootloop showing just Mi logo
3. using different PC, USB port, USB cable, fastboot version, fastbootd/fastboot mode, driver version, Mi flash,.. result always in the same non-functional phone
4. after booting to TWRP (fastboot boot twrp.img), internal data gets decrypted correctly, but TWRP reports issue mounting /odm
5. flashing different ROM version results in the very same issue
Fix:
1. Flash stock ROM (in my case 12.0.8.0)
2. If you receive an CRC error, remove 2 lines from flashing script containing words CRCLIST and SPARECRCLIST and re-run it again
3. Download recovery ROM (12.0.9.0) and put it to internal SD (you can do it in advance or through TWRP when the phone is already "soft-bricked")
4. Flash recovery ROM from TWRP & reboot to functional system
I noticed that fastboot ROM uses super.img, which for some reason isn't flashed properly. Recovery ROM flashes /system, /vendor and /odm partitions directly, which overcomes this limitation. If anyone knows why it happens and especially how to use fastboot ROM directly with no extra steps, please share it.

_mysiak_ said:
I was on stock ROM (12.0.8.0 QJSEUXM) and noticed that v12.0.9.0 is out for some time already, but not offered by system to be installed. In the past with my previous phones when I wanted to "force" the update, I simply downloaded fastboot ROM, flashed it and re-rooted the phone. In a matter of few minutes I had up-to-date and working phone again. Today I tried the same with Mi 10T lite and it failed miserably.
Observed issues:
1. flashing script (flash_all_except_storage.bat) comes with CRCLIST and SPARECRCLIST commands which are either not understood by phone (fastbootd), or fail verification (fastboot)
2. after modification of script and removal of beforementioned lines, flashing completes, however phone stays in bootloop showing just Mi logo
3. using different PC, USB port, USB cable, fastboot version, fastbootd/fastboot mode, driver version, Mi flash,.. result always in the same non-functional phone
4. after booting to TWRP (fastboot boot twrp.img), internal data gets decrypted correctly, but TWRP reports issue mounting /odm
5. flashing different ROM version results in the very same issue
Fix:
1. Flash stock ROM (in my case 12.0.8.0)
2. Download recovery ROM (12.0.9.0) and put it to internal SD (you can do it in advance or through TWRP when the phone is already "soft-bricked")
3. Flash recovery ROM from TWRP & reboot to functional system
I noticed that fastboot ROM uses super.img, which for some reason isn't flashed properly. Recovery ROM flashes /system, /vendor and /odm partitions directly, which overcomes this limitation. If anyone knows why it happens and especially how to use fastboot ROM directly with no extra steps, please share it.
Click to expand...
Click to collapse
I tried to flash firmware rom with mi flash tool, but there error too, maybe i am errorman
i will try one more time, keep your fingers to me

NeverMind._. said:
I tried to flash firmware rom with mi flash tool, but there error too, maybe i am errorman
Click to expand...
Click to collapse
What error? You might need to modify your flashing script and remove lines mentioning CRCLIST and SPARECRCLIST.

_mysiak_ said:
What error? You might need to modify your flashing script and remove lines mentioning CRCLIST and SPARECRCLIST.
Click to expand...
Click to collapse
I will do it on my notebook, if it will show error i will show you it, btw thx for helping me

wtf, i flashd with mi flash tool, after 6 minutes, it shows error, phone is showing redmi lol
btw it works, but now i have redmi 10t lite
{
"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"
}

try this program QPST_2.7.496

i need help. After a failed attempt of flash. My phone stuck on fast boot screen not found in MI flash too. i installed adb again still not appear in mi flash tool. I can enter recovery mode but still not appear in mi flash tool. I only have stock recovery

kammgl said:
i need help. After a failed attempt of flash. My phone stuck on fast boot screen not found in MI flash too. i installed adb again still not appear in mi flash tool. I can enter recovery mode but still not appear in mi flash tool. I only have stock recovery
Click to expand...
Click to collapse
For flashing you need to be in fastboot mode. If your phone is not detected correctly, most probably you have incorrect drivers installed (ADB instead of fastboot). Check from command line "fastboot devices" - you should see your phone connected. If it's missing, check your drivers in Windows device manager.

Can you attach picture , of how many lines did you remove? I have 4 lines with spare and crc

tze_vitamin said:
Can you attach picture , of how many lines did you remove? I have 4 lines with spare and crc
Click to expand...
Click to collapse
Might be easier for you to show the lines.. I removed only 2 lines, but maybe there are more with more recent ROMs.

_mysiak_ said:
Might be easier for you to show the lines.. I removed only 2 lines, but maybe there are more with more recent ROMs.
Click to expand...
Click to collapse
I remove 4 lines but still have the same issue. I reopen MI flash tools, upload ROM again,and still showing the same error, I will upload pics later

I was using my phone normally, I left it charging and when I looked at it again, it would restart non-stop. It's a Xiaomi Mi 10T Lite, I held the power button, but it didn't turn on, it just came back to the bootloader screen, I didn't try to format it as I was trying to recover my files.
So I thought about unlocking the bootloader to get access to my files, I used Mi Unlock Tool, but it doesn't work. I still have access to my account phone number and email address. But I couldn't unlock by this method.
Please I need your help. Thank you

Question Xiaomi K40 Became A Brick

Hi peeps, my Xiaomi K40 now became a brick because it can't be installed any ROM, I've tried using TWRP and also mi flash tool but nothing helps.
When using TWRP I've tried two methods:
1/ adb sideload
2/ Install from a zip file which is pushed to device using adb push command(because now the device doesn't have any OS)
But in both cases it shown:
Failed to mount '/system_root' (Block device required)
Failed to mount '/system_ext' (Block device required)
Failed to mount '/product' (Block device required)
Failed to mount '/vendor' (Block device required)
Failed to mount '/odm' (Block device required)
Click to expand...
Click to collapse
I've also tried to wipe all data using Advance Wipe option to repair the partition but no hope.
Any one has solution for this case? thanks in advance!

Flash your device in EDL mode.
Please refer to the post below on how to bypass edl mode authentication.
[GUIDE] How to bypass authentication and flash in EDL with NO auth for FREE!​
Thanks to VD171 for his post.

I think your device is having a Snapdragon Chipset. Sorry but you may try to search on google for contact to person who has authorised edl account to flash a Snapdragon based phone.

Learn more about it in this video

reborn2020 said:
Hi peeps, my Xiaomi K40 now became a brick because it can't be installed any ROM, I've tried using TWRP and also mi flash tool but nothing helps.
When using TWRP I've tried two methods:
1/ adb sideload
2/ Install from a zip file which is pushed to device using adb push command(because now the device doesn't have any OS)
But in both cases it shown:
I've also tried to wipe all data using Advance Wipe option to repair the partition but no hope.
Any one has solution for this case? thanks in advance!
Click to expand...
Click to collapse
do you still have your fastboot mode on your phone?

mvikrant97 said:
Learn more about it in this video
Click to expand...
Click to collapse
Mi flash didn't recognized my phone.
khazzey said:
do you still have your fastboot mode on your phone?
Click to expand...
Click to collapse
Yes I do.

no bypass for STUCKDRAGON devices for EDL Mode so sad the phone became literally bricked

reborn2020 said:
Mi flash didn't recognized my phone.
Yes I do.
Click to expand...
Click to collapse
listen to me, first if you are on windows 10 you should disable driver signature enforcement on your pc search it on google after disabling you should restart your pc, next step is to install xiaomi flash tool latest (02262021) version after installing the software open it, at the right upper of the software you will see drivers click it and click install after installing, reboot your phone into fastboot mode using volume down and power button, connect your phone to pc and click refresh on xiaomi flash tool if you're phone is detected please come back here let me know

khazzey said:
listen to me, first if you are on windows 10 you should disable driver signature enforcement on your pc search it on google after disabling you should restart your pc, next step is to install xiaomi flash tool latest (02262021) version after installing the software open it, at the right upper of the software you will see drivers click it and click install after installing, reboot your phone into fastboot mode using volume down and power button, connect your phone to pc and click refresh on xiaomi flash tool if you're phone is detected please come back here let me know
Click to expand...
Click to collapse
I did this before but no hope, I don't know if the problem is I'm using a macbook and run windows 10 via bootcamp, I don't have an actual windows computer.
P.S, I upload the latest status.
{
"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"
}

last week I was in a similar situation like yours just twrp and all partition screwed up.
well what saved me was to put dot os 5.2 on a USB c pen drive and then simply installing it from trwp (choosing USB pen as source) after literally 5-10 minutes phones came back to life.
let me know if it works for you.
also if twrp throws any error during installation just ignore them for me after flash completed phone booted just fine

ale82to said:
last week I was in a similar situation like yours just twrp and all partition screwed up.
well what saved me was to put dot os 5.2 on a USB c pen drive and then simply installing it from trwp (choosing USB pen as source) after literally 5-10 minutes phones came back to life.
let me know if it works for you.
also if twrp throws any error during installation just ignore them for me after flash completed phone booted just fine
Click to expand...
Click to collapse
I put a miui rom in a usb type c then connect into my phone, then boot into TWRP, and in Install option, I didn't see any option likes "USB pen"

reborn2020 said:
I put a miui rom in a usb type c then connect into my phone, then boot into TWRP, and in Install option, I didn't see any option likes "USB pen"
Click to expand...
Click to collapse
I said USB pen to make sure you choose it from TWRP install I think the righ name is external storage or something similar anyway it seems you are doing things the right way I am quite sure u ll bring phone back to life.
I think muiu room is just fine, should it fails try crDroid or dot os (do not try arrow or lineage)

Bruh I have a very simple solution I guess it might help you
Well first update to latest official twrp custom recovey for your device then
Navigate to Wipe
advance Wipe
Select data and choose Repair or Change File System
Press Repair File System to see if this fixes the issue. If not, continue.
Press Change File System, choose Ext2, and swipe to confirm.
now switch back to Ext4 and swipe to confirm.
i hope this might help you BTW then flash your first custom rom using a sd card or usb if succeeded then flash every stuff as usual

Anurag3100 said:
Bruh I have a very simple solution I guess it might help you
Well first update to latest official twrp custom recovey for your device then
Navigate to Wipe
advance Wipe
Select data and choose Repair or Change File System
Press Repair File System to see if this fixes the issue. If not, continue.
Press Change File System, choose Ext2, and swipe to confirm.
now switch back to Ext4 and swipe to confirm.
i hope this might help you BTW then flash your first custom rom using a sd card or usb if succeeded then flash every stuff as usual
Click to expand...
Click to collapse
Thanks, I've tried this before, unfortunately still can't solve my problem. Finally I decided to bring my phone to a technician.

Try fastboot erase userdata in cmd after taking your device to fastboot mode
Kinda check different twrp I think your twrp is having any problems plz flash your twrp once again
I hope this will surely work for you my friend.

reborn2020 said:
Thanks, I've tried this before, unfortunately still can't solve my problem. Finally I decided to bring my phone to a ttechnic
Click to expand...
Click to collapse
Bro try different formats then change to Ext4 well try this twrp https://dl.twrp.me/alioth/twrp-3.6.0_11-0-alioth.img.html umm i hope this will help you out completely.

if you still have your fastboot mode (turn off then hold power + vol. down), you should check your pc driver if adb and fastboot driver installed properly, then try flashing stock rom (dont relock your bootloader), I think what cause the brick is encrypted storage that get accessed by twrp, even if you decrypt it using password, you can still brick the phone by manually mount some partition in twrp

Thank you all of your help, peeps. Finally I solved my problem by the help of a technician. Because only technician has access to Xiaomi internal tools, these are "Hardware-Level" which could help in these cases.

He
reborn2020 said:
Thank you all of your help, peeps. Finally I solved my problem by the help of a technician. Because only technician has access to Xiaomi internal tools, these are "Hardware-Level" which could help in these cases.
Click to expand...
Click to collapse
Hello, glad you solved your issue, but can you please explain briefly how hardware was bricked since you were already able to reach fastboot & twrp? Since it's known that when you can boot to fastboot, it's a softbrick

Alipk52 said:
He
Hello, glad you solved your issue, but can you please explain briefly how hardware was bricked since you were already able to reach fastboot & twrp? Since it's known that when you can boot to fastboot, it's a softbrick
Click to expand...
Click to collapse
I can boot to fastboot but I can't do anything with fastboot becuase I wiped out anything on my phone include "firmware" maybe, I don't know, sorry but this's not my major so I can't explain.