Develop Bugs

bricked mi max(?)

hello everybody.
i got a 3/64gb mi max and tried to flash twrp and the miui 8 eu version.
For some reason the phone bricked (flashing the MI logo and then nothing).
i managed to get it on edl mode, i downloaded the official chinese and eu roms but no matter which one i try to flash i get this message and it doesnt go on after that.
any suggestions ?
the phone goes into EDL mode, and also goes into fastboot mode when i keep the vol - and power button. It's working but i can't flash the official rom cause of this message and when i try to flash TWRP, the screen flashes the MI logo and then nothing.

Same problem I had when flashing the latest EU ROM using TWRP with a locked bootloader. Here's what I did to fix it:
1. Make sure you have the latest Qualcomm USB drivers installed
2. Start up Miflash, make sure the right fastboot package is selected
3. Connect your phone to the PC. Hold down Power, Vol- and Vol+ together until you get a short vibration.
4. Check Windows Device Manager. Under Ports, you should see a Qualcomm 9008 QDLoader device. If you see a 9000 port or whatever, disconnect the phone, reconnect it and hold down all three buttons again.
5. Press Refresh in Miflash, you should see a COM10 device. Flashing should be successful.

oatcooky said:
Same problem I had when flashing the latest EU ROM using TWRP with a locked bootloader. Here's what I did to fix it:
1. Make sure you have the latest Qualcomm USB drivers installed
2. Start up Miflash, make sure the right fastboot package is selected
3. Connect your phone to the PC. Hold down Power, Vol- and Vol+ together until you get a short vibration.
4. Check Windows Device Manager. Under Ports, you should see a Qualcomm 9008 QDLoader device. If you see a 9000 port or whatever, disconnect the phone, reconnect it and hold down all three buttons again.
5. Press Refresh in Miflash, you should see a COM10 device. Flashing should be successful.
Click to expand...
Click to collapse
Just tried it. Same message shows up unfortunately

I have the same Problem, bat i use a old Version of Mi Flash. IT works better
Gesendet von meinem Mi Max mit Tapatalk

May i know what windows version you're using it..?, coz old version of MiFlash tool doesn't support running under 32bit system.
Maybe you can try using latest version of MiFlash tool..
You can download it from here..
If official link above doesn't work..just download from here..
Hope it's help..

You must also mark option "Flash all" in MiFlesh.

There is a solution. I have tried everything but mistake was to obvious to posiible really. I was using wrong ROM version to flash it. Had "can not read from port ..." or "can not received hello packet data".
Firts of all download miflash beta. Then check your processor type because this is what define your rom. I thought that my Mi Max 64GB is a hydrogen ROM. Wasted because of that about 30 hours of my precious life Then I realised that my ROM is helium. I downloaded helium_global_images_V8.1.9.0.MBDMIDI_20170103
Flashed it for a first time.
google:
Discussion Solved Bootloop, Cannot receive hello packet, Object reference not set to an

MiFlash: Device in EDL not showing up in MiFlash device list.

Hi,
I was trying to flash Lineage OS on my Whyred, and installed non-ARB ROM over MiUi 10 and my device is now bricked.
I can see my phone in EDL mode, as I can see "Qualcomm HS-USB QDLoader 9008" in the device manager.
I have also installed all the drivers from MiForum thread-784616-1-0. (I don't have right to post complete link)
Even after restart and power cycling the phone, my device does not show in MiFlash tool, and I get "Length cannot be less than zero. Parameter name: length" error. I have tried three different versions on MiFlash tool.
I am on Win10 64 bit
I have unlocked bootloader with TWRP installed before the brick happen.
EDIT:
I tried QFIL methods but it was unsuccessful.
Qfil tool detects the phone without issue, but flashing fails with the following error:
Code:
ERROR: Only nop and sig tag can be received before authentication.

1. none of the custom rom has ARB switched on! how did you brick your phone by flashing Linage??? I cannot understand
2. you cannot JUST go in to EDL mode with RN5pro since Xiaomi has removed the pressing volumes and power button 30 seconds to get in to edl mode! you have remove BACK PANEL of rn5p and short the testpoints with metal & plug the usb in with pc in order to ender edl mode!
3. even if you enter in edl more! miflash will ONLY flash if your MI account has been authorised from china!
now what exactly is your device state? can you reboot enter in fastboot mode?
fastboot roms cannot be placed in LONGGGG paramiters! put it in C drive and rename folders to smaller.. like C:\1 and put all the unzipped Tz files here to flash!
if you cannot flash by mi then you should consider Qualcom Qfil flasher! , RN5p is snapdragon device and can be flashed with QFIL!

YasuHamed said:
1. none of the custom rom has ARB switched on! how did you brick your phone by flashing Linage??? I cannot understand
2. you cannot JUST go in to EDL mode with RN5pro since Xiaomi has removed the pressing volumes and power button 30 seconds to get in to edl mode! you have remove BACK PANEL of rn5p and short the testpoints with metal & plug the usb in with pc in order to ender edl mode!
3. even if you enter in edl more! miflash will ONLY flash if your MI account has been authorised from china!
now what exactly is your device state? can you reboot enter in fastboot mode?
fastboot roms cannot be placed in LONGGGG paramiters! put it in C drive and rename folders to smaller.. like C:\1 and put all the unzipped Tz files here to flash!
if you cannot flash by mi then you should consider Qualcom Qfil flasher! , RN5p is snapdragon device and can be flashed with QFIL!
Click to expand...
Click to collapse
I don't know how it got bricked AFTER installing Lineage OS.
Current situatiuon
1) Mi Flash tool does not list/detect my phone even though I am in EDL mode.
2) Qfil tool detects the phone without issue, but flashing fails with following error:
Code:
ERROR: Only nop and sig tag can be recevied before authentication.

Did you try this method?

[email protected] said:
Did you try this method?
Click to expand...
Click to collapse
Yes, and the above error is after trying this method.

My XIAOMI MI A2 went to 0% and now it has a bootloop android one

I was playing normally the phone discharged turned off, and when I connect it only shows the android one screen over and over, the led that shows that it's charging doesn't turns on, I have nothing weird installed, didn't even knew about fastboot or roms, or anything like that until 15 minutes ago, so the fastboot options are not and cannot be activated, does it have a solution? do I just let it be connected for a few hours and try again, or what, i'm a noob on this matters so I don't know what to do. Thanks

maybe try holding vol down and power for 10 or more seconds. it should vibrate. it reboots and shows fastboot icon, you can flash stock rom again, let us know

loop4444 said:
maybe try holding vol down and power for 10 or more seconds. it should vibrate. it reboots and shows fastboot icon, you can flash stock rom again, let us know
Click to expand...
Click to collapse
The fastboot screen shows, but I can't do anything, and if I connect it to my PC after watching somethings like going to CMD and trying some commands the console doesn't even recognize those commands, maybe I have to install something for it to read it? I don't know, if this helps in anyway, I appreciate it.

M4N4GM said:
The fastboot screen shows, but I can't do anything, and if I connect it to my PC after watching somethings like going to CMD and trying some commands the console doesn't even recognize those commands, maybe I have to install something for it to read it? I don't know, if this helps in anyway, I appreciate it.
Click to expand...
Click to collapse
connect phone in fastboot mode and flash stock rom trough MiFlash, but remember to take backup of internal memory. I'll release all except external sd.

pawelik said:
connect phone in fastboot mode and flash stock rom trough MiFlash, but remember to take backup of internal memory. I'll release all except external sd.
Click to expand...
Click to collapse
Can you do the backup even if the phone can't start? does de MiFlash has that option? and thanks i'll try

M4N4GM said:
Can you do the backup even if the phone can't start? does de MiFlash has that option? and thanks i'll try
Click to expand...
Click to collapse
It seems that you didn´t enable USB debugging before, maybe? Did you solve it?

SubwayChamp said:
It seems that you didn´t enable USB debugging before, maybe? Did you solve it?
Click to expand...
Click to collapse
No I didn't enable the USB debugging, and no I haven't been able to do it, the mi flash program needs extra installations but always sends an error message and closes, I really don't know how to do this kind of things, I tried with a program called MiFlash Unlock, but it needs a Xiaomi account connected with the number and I don't have one, I really don't know what to do from here, plus I've read that I need the rom to install and don't know where can I find it and which one is the one that I need to install.
Once again thanks and if someone can help me further than this is appreciated

M4N4GM said:
No I didn't enable the USB debugging, and no I haven't been able to do it, the mi flash program needs extra installations but always sends an error message and closes, I really don't know how to do this kind of things, I tried with a program called MiFlash Unlock, but it needs a Xiaomi account connected with the number and I don't have one, I really don't know what to do from here, plus I've read that I need the rom to install and don't know where can I find it and which one is the one that I need to install.
Once again thanks and if someone can help me further than this is appreciated
Click to expand...
Click to collapse
Anyway you can't do many things although you should have enabled USB debugging atleast you decided to unlock device but fastboot is (almost) useless for device with locked boatloader.
The first thing I do no matter I don't think to root or modify my device is enabling USB debugging just to have more options to recover from an eventual brick.
Now try to do the next before to go to the other option; try to enter to recovery from device off, using volume up + power for some seconds then format/factory reset and let us know what happened.

SubwayChamp said:
Anyway you can't do many things although you should have enabled USB debugging atleast you decided to unlock device but fastboot is (almost) useless for device with locked boatloader.
The first thing I do no matter I don't think to root or modify my device is enabling USB debugging just to have more options to recover from an eventual brick.
Now try to do the next before to go to the other option; try to enter to recovery from device off, using volume up + power for some seconds then format/factory reset and let us know what happened.
Click to expand...
Click to collapse
That option didn't work, volume up + power just tried to start the phone

M4N4GM said:
That option didn't work, volume up + power just tried to start the phone
Click to expand...
Click to collapse
Ok, I supposed it, some partitions get corrupted while device fails to reboot.
Your last solution is using EDL mode, you will find many tutorials on YouTube to put device in this mode using test point method, then flashing the official stock rom through MiFlash tool.
To take in account MiFlash tool doesn´t work while in fastboot mode on devices with locked bootloaders so you have to use it in EDL (Emergency DownLoad) mode, no other workaround known on that. (for this model)
As reference I´ll put the basis of the links that you need to take a look in:
- Test Point method:
https://www.google.com/url?sa=t&rct...=XzknDcBovWw&usg=AOvVaw3gCAHutdqhO0Ukszyz-XJ-
- Drivers for unbrick qualcomm devices:
https://gsmusbdrivers.com/download/qualcomm-hs-usb-qdloader-9008-driver-64-bit-windows/
- Xiaomi Flash Tool:
https://xiaomiflashtool.com/download/xiaomi-flash-tool-20181115
- Fastboot images, you can use the latest:
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871

SubwayChamp said:
Ok, I supposed it, some partitions get corrupted while device fails to reboot.
Your last solution is using EDL mode, you will find many tutorials on YouTube to put device in this mode using test point method, then flashing the official stock rom through MiFlash tool.
To take in account MiFlash tool doesn´t work while in fastboot mode on devices with locked bootloaders so you have to use it in EDL (Emergency DownLoad) mode, no other workaround known on that. (for this model)
As reference I´ll put the basis of the links that you need to take a look in:
- Test Point method:
https://www.google.com/url?sa=t&rct...=XzknDcBovWw&usg=AOvVaw3gCAHutdqhO0Ukszyz-XJ-
- Drivers for unbrick qualcomm devices:
https://gsmusbdrivers.com/download/qualcomm-hs-usb-qdloader-9008-driver-64-bit-windows/
- Xiaomi Flash Tool:
https://xiaomiflashtool.com/download/xiaomi-flash-tool-20181115
- Fastboot images, you can use the latest:
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Click to expand...
Click to collapse
Thanks i'll try if it works

SubwayChamp said:
Ok, I supposed it, some partitions get corrupted while device fails to reboot.
Your last solution is using EDL mode, you will find many tutorials on YouTube to put device in this mode using test point method, then flashing the official stock rom through MiFlash tool.
To take in account MiFlash tool doesn´t work while in fastboot mode on devices with locked bootloaders so you have to use it in EDL (Emergency DownLoad) mode, no other workaround known on that. (for this model)
As reference I´ll put the basis of the links that you need to take a look in:
- Test Point method:
https://www.google.com/url?sa=t&rct...=XzknDcBovWw&usg=AOvVaw3gCAHutdqhO0Ukszyz-XJ-
- Drivers for unbrick qualcomm devices:
https://gsmusbdrivers.com/download/qualcomm-hs-usb-qdloader-9008-driver-64-bit-windows/
- Xiaomi Flash Tool:
https://xiaomiflashtool.com/download/xiaomi-flash-tool-20181115
- Fastboot images, you can use the latest:
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Click to expand...
Click to collapse
You should try the official and safer fastboot image.
http://c.mi.com/oc/miuidownload/detail?device=1700353

Little Hill said:
You should try the official and safer fastboot image.
http://c.mi.com/oc/miuidownload/detail?device=1700353
Click to expand...
Click to collapse
Wrongly quoted.

[HELP] Bricked Begonia [SOLVED]

My Redmi Note 8 Pro has bricked after flashing Magisk, confused which method can fix my device
- No Recovery (bootloop even holding volume+)
- Can boot to Fastboot but after connect to PC it's rebooting instead connected on fastboot
can somebody help me ASAP

crazyfox21 said:
My Redmi Note 8 Pro has bricked after flashing Magisk, confused which method can fix my device
- No Recovery (bootloop even holding volume+)
- Can boot to Fastboot but after connect to PC it's rebooting instead connected on fastboot
can somebody help me ASAP
Click to expand...
Click to collapse
Can you get it to stop at fastboot, and stop rebooting over and over? Like, when it first powers down (black screen), before it starts to come back up, hold power and volume down, and boot to the fastboot screen. It should stick. From there you can flash stock ROM.
You might need to only flash stock boot.img, but when that's happened to me, I flashed the whole thing

beachfl said:
Can you get it to stop at fastboot, and stop rebooting over and over? Like, when it first powers down (black screen), before it starts to come back up, hold power and volume down, and boot to the fastboot screen. It should stick. From there you can flash stock ROM.
You might need to only flash stock boot.img, but when that's happened to me, I flashed the whole thing
Click to expand...
Click to collapse
Get some info from youtube it seems this laptop fail to detect/install adb/fastboot driver,, then my Device go to charging mode and ended up bootloop instead of charging. (because if i let the phone itself, without connecting to Laptop. . .it's rock solid on Fastboot mode)
Still try to get other PC/Laptop, seems current available one has a messy Windows. . .
When i execute "fastboot devices" on cmd,, pop-out error api-crt-. . . .- l1.1.0.dll missing
Try installing vc_redist failed to execute MSU

crazyfox21 said:
My Redmi Note 8 Pro has bricked after flashing Magisk, confused which method can fix my device
- No Recovery (bootloop even holding volume+)
- Can boot to Fastboot but after connect to PC it's rebooting instead connected on fastboot
can somebody help me ASAP
Click to expand...
Click to collapse
So Sad, was stuck in the same situation tried 100 of methods but all in vain, in the end had to send my device to customer care center & received after 15 days without charges

I use to flash rom`s when i was younger phones and tablets and never had a brick, I am glad it`s out of my system, Anyway the 8pro works fine for me as a non-gamer as it seem to be very risky to flash.
Good luck getting your problem solved.

crazyfox21 said:
My Redmi Note 8 Pro has bricked after flashing Magisk, confused which method can fix my device
- No Recovery (bootloop even holding volume+)
- Can boot to Fastboot but after connect to PC it's rebooting instead connected on fastboot
can somebody help me ASAP
Click to expand...
Click to collapse
crazyfox21 said:
Get some info from youtube it seems this laptop fail to detect/install adb/fastboot driver,, then my Device go to charging mode and ended up bootloop instead of charging. (because if i let the phone itself, without connecting to Laptop. . .it's rock solid on Fastboot mode)
Still try to get other PC/Laptop, seems current available one has a messy Windows. . .
When i execute "fastboot devices" on cmd,, pop-out error api-crt-. . . .- l1.1.0.dll missing
Try installing vc_redist failed to execute MSU
Click to expand...
Click to collapse
Greetings,
First thing I would do is grab the latest version of ADB/Fastboot, uninstall previous version and reinstall it on your Laptop as Admin, turn off your Anti-virus anti-spyware, optimization program or whatever app you may have running on your Laptop and which could prevent system modification, then run it as Admin. If during installation you are poped with installing more things like MS or google's libraries and such, install them.
You may also try to reboot your phone to fastboot while already being connected to computer which may prevent it to boot to the charging page.
If you manage to get fastboot stable enough when connected and if you have no done already, you may want to proceed with reading the [GUIDE][INFO][PSA] Redmi Note 8 Pro - Megathread + CFW and applying the anti-brick solution before flashing anything else like a recovery again.
Assuming you have not damaged anything else, to recovery from a Magisk installation failure you may only need to flash the boot.img from your exact same Stock image you were on.
If that does not suffice, flashing additionally system and userdata (all data will be lost) should fix it.
Hope this helps,
Good Luck!
PS: I am assuming your bootloader is unlocked right?

[SOLVED]
Sorry for late update. . .
Just like i mention above, cause of laptop that i borrowed so messy. . .its anti-core thing won't allow adb/fastboot connection (that's why, my device suddenly disconected and going to charging mode)
*as soon as i go to nearest net-cafe, i can do fastboot thing (Re-flash stock boot.img and TWRP) and my phone booted up normally ??
Edit : my false because i'm forget to close AVB before flashing Magisk

crazyfox21 said:
[SOLVED]
Sorry for late update. . .
Just like i mention above, cause of laptop that i borrowed so messy. . .its anti-core thing won't allow adb/fastboot connection (that's why, my device suddenly disconected and going to charging mode)
*as soon as i go to nearest net-cafe, i can do fastboot thing (Re-flash stock boot.img and TWRP) and my phone booted up normally ?
Edit : my false because i'm forget to close AVB before flashing Magisk
Click to expand...
Click to collapse
So glad you could fix it and make it work in the end! That's all what matters!
You can now mark your thread as "[SOLVED]" by editing original message tittle
Cheers!

Question No valid operation system could be found on G10

Hello There
Just tried to reset the phone from a colleague(forgot his pattern and didnt use his G10 since december 21) and stuck with TFM tool on no command.
Tried every combination with power and volume up but couldn't go further.
With luck after one night of trying the fastboot command on CMD finally found the phone.
First command I tried was fastboot reboot fastboot(found the command somewhere here G10 forum).
The device now wont start in fastboot and start immediately with the AndroidOne logo and afterwards a big red explanation mark with the message:
No Valid operating system could be found.
The device will not boot.
Appreciate any help
Thank you!
Pete

Hey Pete,
I know it's a little late, but I'll put this here just in case you or anyone else needs it later. I got the same error after reset and fixed it by changing the active boot slot.
boot to fastboot
from command prompt/terminal: fastboot getvar current-slot
command will return something like:
current-slot: a
Finished. Total time: 0.002s
In this case you would want to change slot to 'b'
fastboot --set-active=b (if the above says 'current-slot: b', then use --set-active=a here)
fastboot reboot
Then go get a drink or something, this reboot is going to be SLOW.

Dear Experts,
I am having the same error as Pete explained in the beginning, the real problem is I can't get into recovery/fastboot mode by trying different key combinations found in the internet. When I try the combination/ connects usb to PC it shows the error and restart everytime. Even tried to flash stock rom using sp tool but it's not detecting in PC either. Tried a heap of MTK drivers. Tried Test point method. None of these seems to work. Could any super humans among you help me please.
Model - Nokia G10, TA-1334
Thanks in advance..

After a week's research, found the solution and brought back my phone from death. The problem was not the drivers. it was me. Tried the test point method in wrong way, need to set the connection from test point to GND first and then only connect to PC. Also make sure there is at least one program awaiting to be connected (Eg. MTK Client/ MTK Bypass tool).
1. Disable the secure boot.
2. Use SP tool to flash the ROM (Trust me there will be errors. Lots of errors, but it can be sorted with some deep google search).
3. Make sure the test point connected to GND all the time while flashing.
You can do it. Finally, my problem shrinked to the invalid IMEI. will sort it out.

eb60700 said:
After a week's research, found the solution and brought back my phone from death. The problem was not the drivers. it was me. Tried the test point method in wrong way, need to set the connection from test point to GND first and then only connect to PC. Also make sure there is at least one program awaiting to be connected (Eg. MTK Client/ MTK Bypass tool).
1. Disable the secure boot.
2. Use SP tool to flash the ROM (Trust me there will be errors. Lots of errors, but it can be sorted with some deep google search).
3. Make sure the test point connected to GND all the time while flashing.
You can do it. Finally, my problem shrinked to the invalid IMEI. will sort it out.
Click to expand...
Click to collapse
I have the same problem. The phone restarts and I can't put it in fastboot. Could you solve it?

Andrey10 said:
I have the same problem. The phone restarts and I can't put it in fastboot. Could you solve it?
Click to expand...
Click to collapse
You should have back up the firmware before doing anything.
Please try to get the phone in fastboot mode.

I did not make the backup. The combination of buttons to get the phone in fastboot mode does not work for me. All it does is reboot.

Andrey10 said:
I did not make the backup. The combination of buttons to get the phone in fastboot mode does not work for me. All it does is reboot.
Click to expand...
Click to collapse
Have you used SP Flash Tool to reset the device?

eb60700 said:
After a week's research, found the solution and brought back my phone from death. The problem was not the drivers. it was me. Tried the test point method in wrong way, need to set the connection from test point to GND first and then only connect to PC. Also make sure there is at least one program awaiting to be connected (Eg. MTK Client/ MTK Bypass tool).
1. Disable the secure boot.
2. Use SP tool to flash the ROM (Trust me there will be errors. Lots of errors, but it can be sorted with some deep google search).
3. Make sure the test point connected to GND all the time while flashing.
You can do it. Finally, my problem shrinked to the invalid IMEI. will sort it out.
Click to expand...
Click to collapse
hello friend. Did you manage to fix the IMEI by any chance? I have a device that has an invalid IMEI and Serial Number.
I managed to fix the IMEI problem