Related
Hi Guys,
yesterday I was able to unlock my Xiaomi Mi 9T Pro bootloader after waiting for 7 days. The unlock was successfull at first attempt, but now my issues begin and I couldnt find a thread where someone has similar isseues.
1. after unlocking the bootloader, I booted to fastboot mode and flashed twrp (from a greek xiaomi forum website ) after that I tried to boot into recovery. The attempt was unsuccessfull and I got the Mi-Logo Screen with the unlocked message at the bottom, after 60 sec the screen goes black and nothing happens, only fastboot mode is working.
2. flashed back to stock recovery -> the phone boots up successfully and is working.
3. Used the Miflash 2017.4.25.0 Tool to flash fastboot rom to have an untouched condition (clean all option).
4. tried to flash another twrp (from wzsx150), same behavior like in 1. explained. Flashing back stock recovery -> phone boots and is working.
5. again used Miflash to have an untouched condition, tried another twrp (By mauronofrio)
5. same behaviour like in 1. explained...
I actually got a Mi 8 Pro and it was so easy for me to flash twrp (also unoffical builds like now for the 9t pro). Switching to different intel laptops with win7 or win10 didnt solve the problem. Changing USB Type C cabels also didnt help
Can someone explain why I'm not getting things to work, as there are already other members which did it successfully...
Try this...
1. flash TWRP
2. Reboot directly from fastboot into TWRP with volume + and power button
3. Flash TWRP.img with TWRP
Problem solved
Kollachi, thanks for the suggestion but didnt work either.
I found a solution by myself I ordered the xiaomi from amazon DE and it was shipped with global stable, why not EEA? I always used the global stable fastboot rom to start from zero, like mentioned, without success.
The solution was flash eea fastboot rom -> twrp installation worked at first attempt and still works! Interesting that this helped me to solve this..
Left my phone to charge, found it in fastboot mode. When I try to reboot it, no matter what key combination I use, it reboots in fastboot mode. The problem is that the phone is not detected at all over USB. I tried to connect it to both Linux and Windows computers and plugging and unplugging the phone is simply not detected. Any ideas on how to proceed?
I only have a 24-hour period of experience with this phone, but it's strange that it wen't into fastboot during charging.
I will try to point out the main procedures I had to follow after my wife's Mi8 SE freezed after updating with recovery from MIUI 9 (from 2018) to MIUI11 (2020). I had to use platform tools for MacOs to use fastboot commands (mainly fastboot flash recovery to install a new recovery with English language; installed this: https://forum.xda-developers.com/mi-8-se/development/recovery-sky-hawk-recovery-project-2-1-t4051645).
Even after installing this recovery in fastboot mode on a MacOS computer, I had to flash a fastboot firmware downloaded from the Xiaomi Mi8 SE firmware site, only provided for Chinese only firmwares. Had to install the MiFlash and the Qualcomm driver provided for the phone by Xiaomi in a Windows computer, in order to flash the Chinese ROM using MiFlash. After several tries, discovered that I could not let the phone start with the Chinese ROM otherwise, after installing a Global ROM the phone, went back to fastboot... After flashing the Chinese ROM, installed the previously referred recovery in MacOS using the necessary command and afterwards booted into recovery mode (power and volume +), mounted the internal storage, and copied the Global ROM to the phone. Still in recovery mode wiped Cache and Dalvik cache, and installed the Global ROM. After doing this, the phone started correctly with MIUI 11.
I just want to let you know this, in MiFlash I used the mode "Install and delete all". Don't know if this works flashing in mode "Install and keep user data", if you need to maintain your data in the phone.
Hope this helps (I lost our solving my problem).
Hello, i tried to install unofficial twrp for redmi note 9. But ended up bricking my phone.
-The pc can recognise phone(there is windows sound, every 10 seconds)
-Phone is not showing anything
-MiFlashTool v1/v2 cannot see my phone, i used v2 to turn into fastboot but later couldnt reinstall global rom.
Idk what to do now.
The power buttons with holding + or - together.Does that still work ?
Miflashtool what error are you getting ?
What version ROM are you using I use 12.04 global ROM ?
You already installed all drivers and platformtools so that you're pc can't find you're phone normal/recovery/fastboot mode
Can you try to load this file to load in mitools.
Reboot
If your device keep booting in recovery (or blackscreen), you need to erase misc partition.
Here, is the guide for erasing MISC partition: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
Good luck
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
I tried to install custom rom in my device through TWRP and the installation successfully completed but my device dont boot my new OS, it always boot in my custom recovery. I know to install fastboot rom through miui flashing tool but i really dont want to use mi ui, i want to use custom rom. What should i do next???
my device is xiaomi redmi note 9 (merlin) global version
Does the MIUI work normally on a custom recovery?
Mineplayerminer said:
Does the MIUI work normally on a custom recovery?
Click to expand...
Click to collapse
no it doesnot. It only work if i install through fastboot using miui flash tool from windows computer. but when i install custom recovery it starts restarting to recovery everytime
alexwagleofficial said:
no it doesnot. It only work if i install through fastboot using miui flash tool from windows computer. but when i install custom recovery it starts restarting to recovery everytime
Click to expand...
Click to collapse
I'm might trigger the ARB (Anti-rollback) and it prevents you from booting. This may be fixed only by a Xiaomi Authorized repair service. (It's like a ban when you mod a console and try to connect it to the network saying this console is suspended from a network, same on the phone, but it's not permanent unless you re-flash it with the newest MIUI.) The MediaTek chipsets are not good for custom ROMs and recoveries due to their closed-source limitations and support. I would recommend you use the Redmi Note 9 Pro version if you want the Note 9 series phone. It has a Qualcomm and it's really easy to unbrick and re-flash at any time. Try reflashing your phone with the newest MIUI ROM to see if it even boots with the stock recovery.
Mineplayerminer said:
I'm might trigger the ARB (Anti-rollback) and it prevents you from booting. This may be fixed only by a Xiaomi Authorized repair service. (It's like a ban when you mod a console and try to connect it to the network saying this console is suspended from a network, same on the phone, but it's not permanent unless you re-flash it with the newest MIUI.) The MediaTek chipsets are not good for custom ROMs and recoveries due to their closed-source limitations and support. I would recommend you use the Redmi Note 9 Pro version if you want the Note 9 series phone. It has a Qualcomm and it's really easy to unbrick and re-flash at any time. Try reflashing your phone with the newest MIUI ROM to see if it even boots with the stock recovery.
Click to expand...
Click to collapse
Ya you're right buying a mediatek chipset phone is literally one of the biggest mistakes. I cannot even boot my device to edl. Everytime i try to do so, it disconncts automatically
Manjotbenipal said:
Ya you're right buying a mediatek chipset phone is literally one of the biggest mistakes. I cannot even boot my device to edl. Everytime i try to do so, it disconncts automatically
Click to expand...
Click to collapse
My phone disconnects from the USB every 10 minutes of file transferring and then spits out the message that the communication between my PC has failed. At least the DSU mode works so I can enjoy an Android 13 beta experience. I'm switching to Qualcomm or Exynos.
I had soft bricked redmi 4 mobile with locked boot loader, I could go to mi recovery 3.0 and fastboot etc. I tried to flash santoni 10.3 rom via fastboot mode but couldn't flash it with "critical partition error" due to locked bootloader. Then I entered edl mode by shorting test points, then successfully flashed rom with clean all option via miflash tool 'santoni_10.3 global', mobile started well and i used it 2 days. It shows ota updates available of 11.0.2nammixm in setting's updater. I downloaded it and after rebooting it left me mi recovery 3.0 and then I choosen reboot to system and got suck on mi logo again. It means i softbricked device again with locked bootloader. This time i again tried edl mode with miflash tool but it gives error "object reference not set as an object ". Don't know hot fix it. I tried 2 different miflash tool versions, both the fastboot roms "santoni 10.3 global" and "santoni 11.0.2 global" to flash, but getting that error again and again.
Sorry for my bad english.
Please help me, I can go into fastboot mode and edl with port 'qhsusb 9008 com10'
Crying...
Problem resolved,
I got revived again my redmi 4 mobile.
Solution is to try any older rom and older version of mi flash tool.
Suggestions-
Use santoni_global_images_V8.2.12.0.MAMMIEA_20170629.0000.00_6.0_global_751410291c.tgz
And miflash-20220218 or miflash-20170425
Use Edl mode if you have locked bootloader,
Fastboot mode if having unlocked bootloader.
I will update my successes report if get managed to switch on miui 11 (currently having miui 8).