How I (soft) bricked my China set and miraculously unbricked it - Redmi K20 Pro / Xiaomi Mi 9T Pro Guides, News, & D

Other rather I soft bricked it and went into fast boot bootloop but somehow resolved it. Here's what happened:
I followed the instructions and unlocked my phone after seven days. I then proceeded to flash the India rom via fast boot (done this before on other xiaomi devices) as the current custom rom offerings aren't great and are buggy.
Then I think there was either a cable issue or a usb port issue (but I used the same usb port to flash other devices) which resulted in some error when doing fastboot (too many lines).
I then replaced the cable and tried again and it didn't let me flash the latest India rom (again my phone is unlocked and China set ie. Raphael). Telling me incorrect device etc. Not sure if this was the anti roll back issue or just again a cable issue.
I then tried to fastboot flash the china base rom but it failed repeatedly. Any attempt to switch off the phone results in me rebooting to the fastboot page.
Amazingly the computer detects the fastboot device but I'm unable to run any commands eg. Fastboot oem device info etc. It also now tells me that I have an incompatible device to Raphael!! So China set can't flash China rom....
With the last throw of the dice and almost concluding I now have a brick of a phone I decided to change usb port and tried flashing again the latest v15 China fastboot rom. After the third attempt there seemed to be progress... 200+ seconds later an error came up in the miflash tool and I thought here we go again.
To my surprise the phone actually rebooted which was why the error came up.
Thank God it booted and is now working but oh my God what an ordeal I had to go through.....
Sent from my ONEPLUS A3010 using Tapatalk

Related

Fastboot Not Working

So I looked around for this on the forum but I didnt see anything that was working for me.
So I was stuck on a bootloop and couldnt load into recovery (Teamwin) when I was on custom ROM (4.1 JB Rom)
So I ended up sbf a 2.3.6 file. Everything worked fine. I am on 2.3.6 now. However, when i try and run autoscript (http://forum.xda-developers.com/showthread.php?t=1182871) It just says waiting for device when in fastboot.
Is my fastboot broken? I have used fastboot before and have used this autoscript before to unlock the bootloader and flash custom recovery. I am using the same desktop as before as well. Any advice?
This is the only difference I can tell. When I plug my phone into my desktop for RSD it makes a sound that shows its connected and everything. However, when I put fastboot on my phone and plug my phone in the desktop makes another sound (one I never read before). Its not the same sound it used to make when connected in fastboot.
Please help thank you.
Fixed:
I just re-downloaded the drivers from Moto and that fixed it.

Phone bricked and stuck in EDL, won't start after successful flash in MiFlash Tool.

Hello guys, I'm new around here.
This happened the day before yesterday, I had RRemix 6.1 installed on my phone, all of a sudden, mid use, most of the apps stopped responding and nothing was working, so I shut the phone down. Then when I tried to turn on the phone, it wouldn't get past the RRemix loading screen. I waited for a while, then I tried getting into TWRP recovery. In that, the TWRP logo would come then it would suddenly switch to loading the RRemix.
As the RRemix wouldn't open up, I tried flashing MIUI10 global beta through the fastboot method using MiFlash Tool, the flash wouldn't complete so I flashed it manually using fastboot commands through CMD. Then the phone just switched off completely, the display doesn't show a single thing. After a while, randomly, while it was connected to my PC, the red LED started blinking and in Device Manager the device was detected as "Qualcomm HS-USB QDLoader 9008". I searched around and found that this was supposed to be EDL mode.
So, I fired up MiFlash Tool again and tried flashing MIUI10 Global Beta onto it, it returned a message that the flash was successful. The phone is supposed to automatically boot up after the flash according to Xiaomi, but my phone didn't. Now what can I do ? I tried flashing the MIUI9 Stable release too, but even that didn't work.
Thanks a lot.
thereelaman said:
Hello guys, I'm new around here.
This happened the day before yesterday, I had RRemix 6.1 installed on my phone, all of a sudden, mid use, most of the apps stopped responding and nothing was working, so I shut the phone down. Then when I tried to turn on the phone, it wouldn't get past the RRemix loading screen. I waited for a while, then I tried getting into TWRP recovery. In that, the TWRP logo would come then it would suddenly switch to loading the RRemix.
As the RRemix wouldn't open up, I tried flashing MIUI10 global beta through the fastboot method using MiFlash Tool, the flash wouldn't complete so I flashed it manually using fastboot commands through CMD. Then the phone just switched off completely, the display doesn't show a single thing. After a while, randomly, while it was connected to my PC, the red LED started blinking and in Device Manager the device was detected as "Qualcomm HS-USB QDLoader 9008". I searched around and found that this was supposed to be EDL mode.
So, I fired up MiFlash Tool again and tried flashing MIUI10 Global Beta onto it, it returned a message that the flash was successful. The phone is supposed to automatically boot up after the flash according to Xiaomi, but my phone didn't. Now what can I do ? I tried flashing the MIUI9 Stable release too, but even that didn't work.
Thanks a lot.
Click to expand...
Click to collapse
Buy a new one or wait till miui 10 release
yohen_auroville said:
Buy a new one or wait till miui 10 release
Click to expand...
Click to collapse
i.e. I should buy a new phone ?
thereelaman said:
Hello guys, I'm new around here.
This happened the day before yesterday, I had RRemix 6.1 installed on my phone, all of a sudden, mid use, most of the apps stopped responding and nothing was working, so I shut the phone down. Then when I tried to turn on the phone, it wouldn't get past the RRemix loading screen. I waited for a while, then I tried getting into TWRP recovery. In that, the TWRP logo would come then it would suddenly switch to loading the RRemix.
As the RRemix wouldn't open up, I tried flashing MIUI10 global beta through the fastboot method using MiFlash Tool, the flash wouldn't complete so I flashed it manually using fastboot commands through CMD. Then the phone just switched off completely, the display doesn't show a single thing. After a while, randomly, while it was connected to my PC, the red LED started blinking and in Device Manager the device was detected as "Qualcomm HS-USB QDLoader 9008". I searched around and found that this was supposed to be EDL mode.
So, I fired up MiFlash Tool again and tried flashing MIUI10 Global Beta onto it, it returned a message that the flash was successful. The phone is supposed to automatically boot up after the flash according to Xiaomi, but my phone didn't. Now what can I do ? I tried flashing the MIUI9 Stable release too, but even that didn't work.
Thanks a lot.
Click to expand...
Click to collapse
Try flash an older stable rom from miui and hope one boots so u can use phone or flash again to another rom. Download a few different ROMs try them all maybe one is bound to boot up
Test point Only then you can recover your phone.
Gabitozero said:
Test point Only then you can recover your phone.
Click to expand...
Click to collapse
I don't exactly understand what you mean, if I got it into EDL, what's the point of Test Point method, and I don't really understand what the Test point method does.
It will be real helpful of you to explain that to me..
Thanks.
Test point are two point in the mother board.
If you communicate the two points with a wire the phone enters in bootloader mode and you can flash the rom again.
(google test point redmi note 4 and you will get a full imaged guide)
Only for snapdragon version.
I did it succesfully one year ago.
magnus48 said:
Test point are two point in the mother board.
If you communicate the two points with a wire the phone enters in bootloader mode and you can flash the rom again.
(google test point redmi note 4 and you will get a full imaged guide)
Only for snapdragon version.
I did it succesfully one year ago.
Click to expand...
Click to collapse
I did try that, but my phone already shows up as the "Qualcomm HS-USB QDLoader 9008" so it didn't really make any difference, the flashing was successful and the phone still didn't start.. Is there anything else that I can try ?
Install miui 9 with flashtool and it should be fine,
https://sourceforge.net/projects/firmware-global-mido/
Tell me if it worked :good:
BK said:
Install miui 9 with flashtool and it should be fine,
https://sourceforge.net/projects/firmware-global-mido/
Tell me if it worked :good:
Click to expand...
Click to collapse
When I downloaded that, WinRar showed a message that the file was corrupt.
And how do I flash this Firmware using Mi Flash Tool?
Thanks.
Try
Did you try to flesh recovery through ADB?
Alfonso13 said:
Did you try to flesh recovery through ADB?
Click to expand...
Click to collapse
My ADB was turned off, and my device won't turn on, how am I supposed to try that?
Thanks..
Do you try this?
https://forum.xda-developers.com/redmi-note-4/how-to/guide-how-to-edl-flashing-redmi-note-4-t3795831
Alfonso13 said:
https://forum.xda-developers.com/redmi-note-4/how-to/guide-how-to-edl-flashing-redmi-note-4-t3795831
Click to expand...
Click to collapse
That method only works if I could access fastboot, sadly I can't..
same issue i got some days before i removed the back case and remove the battery connection and flashed miui 10 beta without battery connect from mi flash tool i got my same issue but the benefit is fastboot file is recovered after that i flashed orange fox r7 then format all data then install miui10 from orange fox after that phone is booted successfully but persist issue is there (cant receive calls, notification bar not available) but after that i download the miui10 from miui updater (setting-About Phone-System Update-Download Updates) after download the rom flashed from updater reboot the device and success! try this method may be it will works for you also
wont turn on
hey, did u resolve ur problem here? i have redmi 4 prime and stuck in edl mode now.
and samae as your problem here, always success but my phone wont to turn on again, i try every solution in this forum and other. the result still same til now, 3 days already and still same. please help me, before my mom kill me cause this phone wont turn on.
sorry for bad english
hi everyone, so i am having an issue with my xiaomi mi a1. I rooted the device in order to install the pixel 3 g-cam, yesterday i tried to unroote it and to lock its bootloader but as i was doing this, the system was destroyed. i flashed the device and got it working, the my GF tried unrooting it from magisk app and i dont kow what happened it appeared th co command symbol. I flashed it again and everything was normal util the mi screen appeared and then the android one logo show. the next thing that happended was the advise of corruption, the mi screen and android logo. again and again so on so forth. i've flashed the device, several times and nothing changes. i've locked and unlocked the bootloader, and nothing. I even tried stock recovery options but resuts in the same. what esle can I
do ?
I may be late but something like this happened to me as well.
I got my phone bricked and because I was in school the phone was stuck on booting screen for a long time. When I got back the phone's battery was dead. I put it on the charger and it wasn't doing anything, all of a sudden it starts to blink red light (sign it's in edl mode) I don't quite remember if I got into the fastboot and then flashed miui 9 beta with a pc through the miui application idk what it's called and after the installation was over it worked. It could be a problem with not being in the right mode (as I said previously it's either edl or fastboot) or it could be because of a problem with that miui version
Maybe Anti-Roll back problem?

Urgent Help. Hard-bricked my device in warranty.

I have hard bricked my device, even motherboard is dead, no sound when connected to PC. Phone is in waranty. What should i say to realme support so they won't be able to tell that I tried to install custom ROM and charge me for motherboard. It's a new phone. I unlocked the boot-loader.
Deepakk88 said:
I have hard bricked my device, even motherboard is dead, no sound when connected to PC. Phone is in waranty. What should i say to realme support so they won't be able to tell that I tried to install custom ROM and charge me for motherboard. It's a new phone. I unlocked the boot-loader.
Click to expand...
Click to collapse
best bet is to visit SC and tell them your device stopped working after official update . don't say anything else
I told them that the phone failed to start after a software update. They repaired it in 2 hrs and gave it back. So the motherboard was not fried as I thought.
What happened was that the TWRP recovery someone provided here has not worked, my device failed to get in to TWRP recovery after I have re-started the phone, So, I tried to flash with other TWRP versions that some people linked to in their posts on Realme U1 on other websites. None of them worked and after sometime my phone went in to bootloop, I got it in to fastboot screen by holding down the power and vol down button and tried various fastboot commands, none of them fixed the bootoop. I finally gave the command 'fastboot oem reboot -recovery' then it switched off the phone.

Another Brick Oreo and TWRP mess

Hi guys been spending all night trying to figure out but seems nothing is working. HELP! I know i can get it to work.
So tried to root my A2017G previously but saw all the horror brick stories so ended up just doing the multiple OTA updates via SDCARD upgrade.zip and finally ended up with OREO BO3 version. running fine except for ridiculous battery meter levels playing up but just kept it charged most of the time.
1) at first I tried to check bootloader unlock status from fastboot. But somehow unable to as fastboot is not there! So i thought maybe fastboot is corrupt (stock recovery options ok / also power plus down gets stuck in FTM mode (easy to reboot with adb command) So unable to check bootloader (i am thinking its probably still locked)
2) so got latest version of TWRP 3.3 something and flashed it --> result in phone black screen but detectable (I assume in EDL mode.) '
3) Tried to flash Nougat B10 EDL with EDL tool (working now but after everything is ready to flash it says"" 13:02:38: {ERROR: WritePort:5164 Could not write to '\\.\COM8', Windows API WriteFile failed! Your device is probably *not* on this port, attempted 100 times""
4) MiFlash unable to read hello packet. But i tried pressing power and connecting quickly and suddenly starts flashing B10 nougat EDL ROM but doesnt complete with a "function: sahara_rx_data:237, unable to read packet header" error. Should I be using a stock rom with Meta-INF folder rather than the EDL version? Also should i be flashing OREO stock rom rather than nougat with MiFlash? or it doesnt matter?
5) tried the DFU tool initially qualcomm and com8 detected but says disconnected. (so its in EDL probably but somehow still disconnected?
So currently
1) trying to let the phone battery run out, though i doubt its any use as i probably bricked it installing twrp without unlock bootloader on OREO.
2) Also downloading Oreo stock rom to try and flash with miflash.
Any help or point to some discussion i missed would be helpful thanks. Just wanna get root and GPS tools running so I can let the kids catch some Pokemon without GOing outside.
Seems like the battery had to run out first. Then it started recharging . After about 5 mins I just pressed power button without up or down. Phone rebooted nicely back into Oreo. PhEW... Then i used a stock 2017g EDL for nougat B10 (7.1.1) and flashed with Miflash by going into proper EDL (used ADB reboot EDL command)
Ok some more small hiccups along the way but being able to access EDl i managed to flash TWRP 3.2.1 and then load it up and flash SuperSU for root.
Now to read the threads on how to get rid of the bootloader unlock screen as well as load in the battery saving scripts.

Mi a3 hard brick, Screen Black, Haven't opened the backside of my phone yet.

Hi, I beg your help. Well what happened is,
I was on CORVUS OS, then I thought of rolling back to stock rom. So after flashing "laurel_sprout_global_images_V12.0.21.0.RFQMIXM_11.0" using Mi Flash tool (clean and unlock), My phone said to me "This device has been destroyed". So I thought I might have flashed a wrong version. So I again flashed "Xiaomi_Mi_A3_V10.3.4.0.PFQMIXM_20190815.0000.00_Global_9.0_XFT" using Mi flash tool. But this time, android one logo showed up and did'nt proceed. Luckily I could access to fastboot mode. But after doing this flashing few more times, My phone blacked out completely. Things I have done so far:
1. Tried flashing again using Mi flash tool. The device manager says that the "QDloader 9008" is connected properly, but the flash tool is saying "cannot receive hello packet" and eventually fails the proccess.
2. Tried volume button and plugin combination. Nothing happened.
3. Download QFIL software. But it's not detecting any device.
4. Tried switching USB port
Please save me. I am going through a disaster. and it's my primary driver T_T
try to disconnect the battery, and plug usb
Try flashing using Paltform-Tools instead of Mi Flash Tool. See https://forum.xda-developers.com/t/slot-a-is-destroyed.4399965/ for links to instructions.
Do not take the back off your phone. Seriously, shell out the ten bucks for the deep flash cable. You need to get to EDL. Here are a couple of methods, depending on what you want:
Repackaged A11 stock here: https://c.mi.com/thread-3527044-1-0.html
CC9e Conversion here: https://forum.xda-developers.com/t/miui-12-port-10-miui-12-for-mi-a3-stable-weekly-rom.4016457/
Note: If you want to use QFIL, make sure you're using the latest version with QPST. Save yourself the time and install it system wide. https://qpsttool.com/qpst-tool-v2-7-104

Categories

Resources