Develop Bugs

Used One X, boot loop then out of battery

Hi,
I really truly tried to resolve my issue (by searching etc.) and learned a lot along the way but I have the problem still.
I bought a used One X. The guy showed me Jelly Bean working on it. I didn't use it at the sale. After I got home I found it was stuck on the HTC start screen. I had to go and it wouldn't turn off so I left it for half a day.
Found the volume down and power trick and booted several times into recovery mode and clockwork. Eventually tried format SD in clockwork. I also found a factory reset or similar button somewhere (can't quite remember if it was in recovery or clockwork). I think it was then that I had no more clockwork. Got a loop into Fastboot, message at the top says "Relocked - Security Warning". Can't switch it off. It occasionally switches itself off doesn't respond to the power button, after a few minutes with a usb plug in it starts again. It turns itself off after 15-20 mins again. When in Fastboot all options just loop back to Fastboot although reboot bootloader takes more time and has more lights.
Eventually started using fastboot cmd. Got an unlock token to flash, received error Failed (remote: battery low). Continued to receive that error with whatever I tried.
Found forums on using wires on the battery to charge and cycling reboots without success. As far as I can tell you can't get to the battery of the one x and I don't get the HTC flash screen mentioned in the cycling solution anymore.
Can I charge this phone? Should I investigate taking it apart to access the battery? Will a phone shop be able to fix this problem by doing things I can't?
Thanks for your time.

Here's your solution
http://forum.xda-developers.com/showthread.php?t=1738274

ArmedandDangerous said:
Here's your solution
http://forum.xda-developers.com/showthread.php?t=1738274
Click to expand...
Click to collapse
Great! Thank you very much A&D. I downloaded and installed Android SDK, got the file and put it in the right folder, now I need to open a cmd window and type "adb ???? fastboot-battery-recharge.bat" in order to charge the phone. Can you help?
Thanks

Just extract the Fastboot-battery-recharge.bat and put it into your platform-tools folder inside your Android folder (assuming you have downloaded the SDK).
Now enter fastboot (power and Vol Down) and double click the .bat file and let it do it's work
Another source for you
http://forum.xda-developers.com/showthread.php?t=1840156

Great thanks, it's going. I didn't realise it was a batch file.
One problem is that my voltage is going down not up, happy to leave it for a while though. Started at 2877mV and now is 2858mV after about 50 cycles. You can see it going up sometimes and down others but overall is going down...
IMPORTANT: I figured out you need to use a short usb cable and avoid front panel and bracket usb slots

Weird. Your phone is still connected right? It should be charging but takes a long time. If all else fails, HTC is your only help ):

Hi,
I have the same problem but i can't get ADB to work on mac osx.
I can't get to recovery because the battery is to empty, i can't get to flash a boot.img because batt. is empty.
does anyone have a solution?

The battery is up after 30 mins to 2960mV so it does work overall.
fvanommen said:
Hi,
I have the same problem but i can't get ADB to work on mac osx.
I can't get to recovery because the battery is to empty, i can't get to flash a boot.img because batt. is empty.
does anyone have a solution?
Click to expand...
Click to collapse
The batch file contents are as follows:
@echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
You could write your own batch for use with mac (assuming mac's can run fastboot.exe)...or just type it out for 6 hours straight

fishy12345 said:
The battery is up after 30 mins to 2960mV so it does work overall.
The batch file contents are as follows:
@echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
You could write your own batch for use with mac (assuming mac's can run fastboot.exe)...or just type it out for 6 hours straight
Click to expand...
Click to collapse
Glad it's working! Gonna take many hours to get that charge up, but at least it's working xD

fishy12345 said:
The battery is up after 30 mins to 2960mV so it does work overall.
The batch file contents are as follows:
@echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
You could write your own batch for use with mac (assuming mac's can run fastboot.exe)...or just type it out for 6 hours straight
Click to expand...
Click to collapse
I have the same problem, the HTC screen is coming up the led is burning and than reboot (in about 5 sec).
My Battery is charging with every reboot very slow but it is charging.
From 1% to the required 3474mV was 12 hours of charging (about (8640 reboots :silly
Now i am on 3487mV but this is still not good enough.
I will let is charge for a little while hoping it will work again.

Solved - "FAILED - Remote (battery low)" error
fvanommen said:
I have the same problem, the HTC screen is coming up the led is burning and than reboot (in about 5 sec).
My Battery is charging with every reboot very slow but it is charging.
Click to expand...
Click to collapse
Yep it's a common problem by the sounds and hopefully this thread will stand out as the one to use.
Basically if you receive a "FAILED - Remote (battery low)" error through fastboot you should use the command "fastboot getvar battery-voltage" and find out how far from the required 30% (how low the mV number is / highest mV the battery holds = [> or < 30%]), this will vary from phone to phone. If you are under the threshold and have the older boot loader you will not be able to charge your phone by leaving it plugged in and hoping. You are have 3 options:
1) If your phone has a removable battery you can the wiring from an extra usb cable in order to get charge or just put in a charged one - the One X cannot use this solution
2) If it is close to 30% you might be able to get enough charge by rebooting it 10 or 20 times (this is because for a portion of the boot up time the phone takes on charge). The report of this solution working involved the ph boot looping onto the HTC splash screen, my ph was looping into boot loader only.
3) If it is far enough off the correct mV, you can run a batch file (props to Laav) that loops 2) and reports battery voltage until you are satisfied. This requires a USB connection and you should use a short usb cable and avoid front panel or bracket slots (especially if you notice that the voltage doesn't always increase each reboot).
Once you get to 30% you are able to flash imgs using fastboot and I would recommend (as Laav does) flashing the newer Clockwork Recovery which allows you to charge the phone while in recovery mode. Then let it charge to 100% and worry no more that you'll get caught out.
If you are reading this and don't have this problem, make sure your clockwork is up to date so you don't end up with it (ie. having a problem with your rom and needing flash tools with a battery below 30% leaves you with no way to charge it).
From my experience the batch file method increased my battery voltage 300mV in about 3 hours so 100mV/hr is probably a reasonable guideline.

I'm sorry actually it's not working for me. Just checked the voltage and it's 2960mV. Because it's not my phone I don't know if it had a battery problem or anything. Is there no way around the 30% check?
The receipt says it was purchased on 24.4.12...

This tutorial thread says 30% = 3478mV
With battery-voltage: 3490mV
sending 'boot' (4466 KB)... OKAY
writing 'boot'... FAILED (remote: battery low)
Others say it has to be over 3680mV, i think this is the correct value. But i don't have that value so i have to wait until then to check.
I have the clockwork recovery but it is not loading, when i press recovery i see the clockwork logo about 1 sec and then it reboots.
For now i wil leave it to the charger for 7/6 hours and let it reboot every 5 sec, i hope this will get me enough power.
Is there someone who can make the batch work on OSX?
Thanks

2819mV now...2781mV 3 mins later... I guess aside from installing a new charged battery or sending it to HTC I'm sunk. I'll call a phone repair store and see if they'll change the battery and flash the new clockwork or stock rom for me tomorrow...
Does anyone suggest a change to the batch file/timing to see if that works? To make it longer do I change the "ping /n 6 localhost >nul" to a larger number?
Are other people getting a constant increase when they look over the voltages reported?

fishy12345 said:
2819mV now...2781mV 3 mins later... I guess aside from installing a new charged battery or sending it to HTC I'm sunk. I'll call a phone repair store and see if they'll change the battery and flash the new clockwork or stock rom for me tomorrow...
Click to expand...
Click to collapse
OMG! I found something v. important out, I was using a long usb cable (1.5m) and a usb slot on the computer that is a bracket (rather than the motherboard slots) and once I changed over to a very short cable (10cm - I have it for the car) and the motherboard usb slot I'm almost charged up in 10 mins. I'll edit the longer post now.

Received error "FAILED: remote (not allowed)" when trying "fastboot flash recovery recovery.img"

If your bootloader is unlocked, just flash CWM touch recovery whilst the phone is in fastboot.
http://db.tt/VF9J2eo8
Place it in the same folder as fastboot in Android SDK,
Enter fastboot
Plug in usb cable from PC to phone
Should now say fastboot USB
Open command prompt
cd c:/Android-SDK/platform-tools
fastboot flash recovery CWM.img
Sent from my HTC One X using Tapatalk 2

fvanommen said:
This tutorial thread says 30% = 3478mV
With battery-voltage: 3490mV
sending 'boot' (4466 KB)... OKAY
writing 'boot'... FAILED (remote: battery low)
Others say it has to be over 3680mV, i think this is the correct value. But i don't have that value so i have to wait until then to check.
I have the clockwork recovery but it is not loading, when i press recovery i see the clockwork logo about 1 sec and then it reboots.
For now i wil leave it to the charger for 7/6 hours and let it reboot every 5 sec, i hope this will get me enough power.
Is there someone who can make the batch work on OSX?
Thanks
Click to expand...
Click to collapse
A couple of hours later my battery did not charge ant more and is stuck at 3490mV.
Is there any other way to load my battery?

fvanommen said:
A couple of hours later my battery did not charge ant more and is stuck at 3490mV.
Is there any other way to load my battery?
Click to expand...
Click to collapse
You should still be able to flash ClockworkMod & a custom rom.
You could do this, even if to at least get your phone up and running to charge it fully.
Sent from my HTC One X using Tapatalk 2

fvanommen said:
A couple of hours later my battery did not charge ant more and is stuck at 3490mV.
Is there any other way to load my battery?
Click to expand...
Click to collapse
I found the same thing, it wouldn't go past this but it was enough to change the message from Battery low to (in my case) Not allowed.
I had locked the bootloader but it wouldn't unlock so I locked it (sent command twice and received 'ok' message). Unlocked the bootloader again, realised how the menus/options on stock bootloader actually work, loaded clockwork recovery through the recovery option (it was on there the whole time), went back out and made sure it was up to date, used it to install a new Jelly Bean copy, charged the phone.
Well, it took 12 solid hours of researching and attempts after I initially bought what was supposed to be a working phone but it's back again.
Thanks to all who contributed to my questions.

[Q] HTC One X screen not getting turned on

Hi Guys
I have an international version of HTC One X. I installed many ROMS and at last when i was in Slim Rom, screen showed sme thing like scratches and it got turned off. After that i tried booting up in recovery,boot loader and all. But the screen wont turn on,leaving red indication led on and a vibration. In between it turned on and i thought of going back to stock and i relocked boot loader. After that its not being charging and where i try flash to stock it shows Battery Less than 30%. How much i plug in ..it wont charge.
Again the screen went off and i tried the scrip t[" @ECHO off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start" } for making it at least to 10 % .on the first try it became 10% and it booted int o boot loader and it was showing locked in boot loader. I tried to unlock it again .I showed confirmation screen from HTC and i confirmed but still boot loader showed "LOCKED"..
Again the screen went off and it didn't boot to boot-loader. It again shows the red led indication on and it gives a vibration feedback when ever i press the power button for a long time.
Now when i Plugin to wall charger this led notification stays for sme minutes and it gets turned off.
Is there any Solution For this? Please help me out guys..

Jabron1 said:
Hi Guys
I have an international version of HTC One X. I installed many ROMS and at last when i was in Slim Rom, screen showed sme thing like scratches and it got turned off. After that i tried booting up in recovery,boot loader and all. But the screen wont turn on,leaving red indication led on and a vibration. In between it turned on and i thought of going back to stock and i relocked boot loader. After that its not being charging and where i try flash to stock it shows Battery Less than 30%. How much i plug in ..it wont charge.
Again the screen went off and i tried the scrip t[" @ECHO off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start" } for making it at least to 10 % .on the first try it became 10% and it booted int o boot loader and it was showing locked in boot loader. I tried to unlock it again .I showed confirmation screen from HTC and i confirmed but still boot loader showed "LOCKED"..
Again the screen went off and it didn't boot to boot-loader. It again shows the red led indication on and it gives a vibration feedback when ever i press the power button for a long time.
Now when i Plugin to wall charger this led notification stays for sme minutes and it gets turned off.
Is there any Solution For this? Please help me out guys..
Click to expand...
Click to collapse
run the script for at least 4 hours then power down your phone from the bootloader and plug into a wall charger until it is fully charged. Also, never flash anything unless you have at least 70% battery

nogotaclue said:
run the script for at least 4 hours then power down your phone from the bootloader and plug into a wall charger until it is fully charged. Also, never flash anything unless you have at least 70% battery
Click to expand...
Click to collapse
I ran the script more than 4 hours ..but still it doesn't give any value more than 3720 mV and it didn't turn on.

M9 issues after update

Hello everyone,
a friend of mine is having problem with his M9. He recently downloaded an update to the phone, but after restart the phone no longer boots, says 0% battery and would not charge (just keeps heating). After a while on the charger it tries to boot (white screen with HTC logo), but after like 20 seconds it reboots.
I can make it enter the "service menu" (or how is it called) - white screen saying "Software status - modified, LOCKED, S-ON" and some menu items (I would post a picture but the forum won't let me because I am new...)
the problem is that Recovery mode does not work, there is just black HTC logo in infinite reboot loop. Reboot to bootloader just reboots to the same menu. The download mode basically says "Failed to boot to download mode. This build is for development purposes only..."
If I plug the phone to PC, while the menu is present, I hear a sound that is was plugged to PC, but a second later it's unplugged, so I was unsuccessful trying to make some sense to it using ADB.
Can the phone be saved? Thanks for help

Whats annoying is that the phone keeps rebooting until it runs out of battery power, I haven't found a way to prevent it from rebooting. So-called "smartphone"...

I tried to update the firmware using RUU_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.23.617.1.exe, but it said I don't have sufficient battery charge. So I plan to use the Fastboot-battery-recharge.bat overnight to give it a charge.
The problem however is that the command
Code:
fastboot getvar battery-voltage
returns "battery-voltage: " without the voltage itself. Anyone experienced this? I am using the latest minimal ADB and fastboot (1.4.3)

BTW the phone is originally EE UK.

Boot loop issue: cannot get into fastboot from "no command" screen

Hey everyone,
A2 lite phone is in bootloop - allegedly (not my phone) "out of nowhere". The user does not do any fancy things like flashing, and this has not been done either.
Phone is on continuous boot loop, and sometimes (really seems randomly), the device starts up in the "no command" mode and stays there for a while. I read that we could go into fastboot mode by pressing "power button and tapping volume up key", but this doesn't do anything.
I've tried this thread: https://www.the***********.com/boot-xiaomi-mi-a2-fastboot-mode-recovery-mode/
But I'm not even getting into fastboot.
I'm almost thinking that the volume buttons are just broken, though from the feedback of the buttons this doesn't seem realistic.
EDIT: ok, now I'm somehow able to get it into fastboot.... sometimes. Now I'm here:
I switched the partition from a to b, but it still goes into bootloop. Then I switched it back to a, still bootloop. Then back to b. Still bootloop! But at least now sometimes I'm able to get into fastboot. No matter what kind of commands I'm typing in the cmd console, after about 10 seconds on the fastboot screen, the phone just reboots.
idk, it looks almost as if both partitions have the bad android 10...
Do you guys have any idea? Please let me know if more info is helpful.

You go into fastboot mode by holding Vol Down + Power button. So try holding Vol Down and Power button at the same time to go into fastboot mode. (Don't tap it)
Go here and grab the image you prefer (latest should do the trick) : https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Then go ahead and follow this guide here to flash the stock ROM : https://c.mi.com/oc/miuidownload/detail?guide=2
This will wipe the data on the device, but it seems like you have no other option at this point. Cheers.

Thanks! I've tried that now. It starts flashing the device until... after about 10 seconds, the phone reboots from Fastboot mode .

As per this page: https://twrp.me/xiaomi/xiaomimia2lite.html
I've tried to do a recovery via TWRP. If I execute `fastboot boot path/to/twrp.img` then I go from fastboot to TWRP (the teamwin logo), but right after that the phone already reboots.
https://www.xda-developers.com/how-to-install-twrp/ - I don't know if it means anything, but when I execute `adb reboot bootloader`, the console returns `error: no devices/emulators found. If I execute `adb devices`, it does not list my device. However, if I execute `fastboot devices`, my device is listed.
I installed ADB usb drivers, so when I get my phone connected in fastboot, it shows up as Android Bootloader Interfacee in device manager. So not sure what's going on here, but it's all weird.
What I'm facing is very, very similar to https://www.reddit.com/r/Xiaomi/comments/4ltzt9/xiaomi_mi_note_boot_loop_even_in_fastboot/ <-- but that thread is a bit of a dead end (and 3 y/o)...

daize said:
after about 10 seconds, the phone reboots from Fastboot mode .
Click to expand...
Click to collapse
Hmm, it should never do that, maybe it's a hardware issue that we can not fix via Fastboot ?
daize said:
As per this page: https://twrp.me/xiaomi/xiaomimia2lite.html
when I execute `adb reboot bootloader`, the console returns `error: no devices/emulators found. If I execute `adb devices`, it does not list my device. However, if I execute `fastboot devices`, my device is listed.
Click to expand...
Click to collapse
When the device is in Fastboot mode, it will only be recognized as Fastboot. Only when it's properly booted, the device can be recognized in ADB, so no issues there.
I assume your bootloader is already unlocked as you have successfully booted into TWRP. You might try EDL (Emergency Download Mode) flash as a last resort :
Download MiFlash (20160401) from here : https://www.xiaomiflash.com/download/
You're downloading that particular version because it is able to EDL flash on your phone. Install the MiFlash you've downloaded and open it, then put the phone into fastboot mode. Connect it to your PC and use this code to take the phone into EDL mode:
Code:
fastboot oem edl
After you hit enter, you will see the screen turn off and notification LED blinking, this is normal. This means the phone is in EDL mode. Open the MiFlash you've installed (likely in C:\Program Files\Xiaomi\MiPhone) and browse to the ROM location and connect the phone. Choose "Flash All" and start flashing.
After the EDL flash is complete the phone will not reboot. It will stay in EDL mode. You need to disconnect the phone from PC and hold power button (about 10-15 seconds) to boot the phone. If the phone boots properly, you can go into fastboot and connect it to PC, then use:
Code:
fastboot oem lock
to relock your bootloader. Try it and let me know. :fingers-crossed:

Thanks for the continued help!
I've followed your steps - When I run fastboot oem edl, the console returns "... okay [ 0.0202s] finished. total time: 0.022s" and the phone turns to a black screen (no notification led blinking). Then... after a couple of seconds, goes back into the boot loop .
Something maybe to note: every time that my phone starts up, it (1) shows a screen saying "Your device software can'tbe checked for corruption.Please lock the bootloader.", and then slides down to the typical "androidone" white screen before it reboots again.

daize said:
every time that my phone starts up, it (1) shows a screen saying "Your device software can'tbe checked for corruption.Please lock the bootloader.", and then slides down to the typical "androidone" white screen before it reboots again.
Click to expand...
Click to collapse
The screen with the ugly text is normal, since you have an unlocked bootloader, it's there to warn you that the device's software might've been tampered with. On the main subject though, I'm out of ideas. You might try booting the phone by holding Power + Vol Up, which should normally boot into stock recovery or wipe the data on the device. But I'm slowly beginning to think that this might be a hardware issue rather than a software issue that I can help you to fix.
Under normal circumstances, EDL flash is the way to fix any problems you might encounter with the software, that's why it's called the Emergency Download mode. But since we're past that stage, I believe I will not be able to assist you further. Hope you can fix your device my dude/dudette!

If the phone gets out of fastboot mode your phone does not get recognized from your computer. Try to delete fastboot and minimal adb and download the latest version. [https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445]
Open MiFlash, click Driver left on the top and install them.
Set path to the downloaded firmware. Now boot into fastboot, once that is done connect your USB cable to both, computer and phone. If this doesn't work try different USB-Ports and USB-cables. Some work, some don't. This might be the reason for leaving the fastboot mode.
Click refresh and see if your device appears

@marstonpear thanks for your help so far <3 @Cappucinto, thanks for chiming in! What do you mean with this: "Open MiFlash, click Driver left on the top and install them." <-- in MiFlash, I do not see an option to select driver...

@marstonpear thanks for your help so far <3
 @Cappucinto, thanks for chiming in! What do you mean with this: "Open MiFlash, click Driver left on the top and install them." <-- in MiFlash, I do not see an option to select driver...

What did change now after installing these drivers: https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445]
I did try some other USB cables. The one I've been trying triggers the windows sound for "new device successfully connected" when I boot the phone up in fastboot, and then of course gives the "device disconnected" sound when the phone then reboots. With another USB cable in this case, windows just states: "USB device not recognized". So it seems like the cable I haven't been using is defect .

I'm unable to use MiFlash at the moment so I can't explain the whole procedure with installing the drivers in MiFlash. But there has to be something like "Install > Drivers" or something. Maybe someone else can help out.
Try to use the working cable again, open a command prompt and type: fastboot devices
Then wait for an answer, post it here and see if the phone reboots again or if it stays in fastboot

daize said:
Hey everyone,
A2 lite phone is in bootloop - allegedly (not my phone) "out of nowhere". The user does not do any fancy things like flashing, and this has not been done either.
Click to expand...
Click to collapse
The response by marstonpear below makes sense.
marstonpear said:
You go into fastboot mode by holding Vol Down + Power button. So try holding Vol Down and Power button at the same time to go into fastboot mode. (Don't tap it)
Click to expand...
Click to collapse
Although u shd consider this link, i tried to arrange it step by step:
https://forum.xda-developers.com/sho...php?p=79365091
Follow the instructions, as dat was how i revived mine. Hopefully it may help u.
Note; wen using twrp, preferably use " twrp - offain "
Miflash tool:
Link 1: https://www.xiaomiflash.com/download/
Preferably use Link 1 & choose either 2016, 2017 or 2018 versions. They come preloaded with the drivers u need
Link2: https://xiaomibuzz.com/downloads/download-xiaomi-mi-firmware-flash-tool-latest-version-2018.html
Lets know how it goes

Cappucinto said:
I'm unable to use MiFlash at the moment so I can't explain the whole procedure with installing the drivers in MiFlash. But there has to be something like "Install > Drivers" or something. Maybe someone else can help out.
Try to use the working cable again, open a command prompt and type: fastboot devices
Then wait for an answer, post it here and see if the phone reboots again or if it stays in fastboot
Click to expand...
Click to collapse
Hey there When I get into fastboot and run `fastboot devices`, a code returns <tab> fastboot.
... and then the phone restarts I'm trying but I guess I'm beyond the stage of being upset, haha.
@agbadino https://forum.xda-developers.com/sho...php?p=79365091 <-- that first link seems to be broken, could you check again? I'd love to try your steps!

daize said:
@agbadino https://forum.xda-developers.com/sho...php?p=79365091 <-- that first link seems to be broken, could you check again? I'd love to try your steps!
Click to expand...
Click to collapse
Sorry bout d previous link. I believe this shd take u directly to the tutorial:
https://forum.xda-developers.com/mi...tboot-mode-t3920925/post79365091#post79365091
remember to use "twrp offain for daisy". It works better than the regular twrp for daisy
It my take and procedure that worked for me at the time. Good luck tho

Thanks! Sadly, when I get to the `fastboot oem edl` step, it fails. I get into fastboot, I quickly enter `fastboot oem edl`. CMD says finished, the screen turns off. I immediately refresh in MiFlash (COM3 is the device), I start flashing. After 4 seconds, the device turns off (windows sound "device disconnected"). The flashing runs for a total of 7-9s says "the operation completed successfully.(0x000000000: cmd <?xml version="1.0" ?><data .. etc etc
So I don't really know what to do if I can't get into EDL mode .

daize said:
Thanks! Sadly, when I get to the `fastboot oem edl` step, it fails. I get into fastboot, I quickly enter `fastboot oem edl`. CMD says finished, the screen turns off. I immediately refresh in MiFlash (COM3 is the device), I start flashing. After 4 seconds, the device turns off (windows sound "device disconnected"). The flashing runs for a total of 7-9s says "the operation completed successfully.(0x000000000: cmd <?xml version="1.0" ?><data .. etc etc
So I don't really know what to do if I can't get into EDL mode .
Click to expand...
Click to collapse
Try getting another chord and try again.

Tried some other cables. Every time I run fastboot oem edl, it keeps saying "finished", and then reboots the phone in about 5 seconds. One time, it said "Catastrophic failure" as "status" for the flashing.
Otherwise, it most often says "The operation completed successfully.(0x00000000: cmd <?xml version="1.0"?><data><patch SECTOR_SIZE_IN_BYTES="512" byte_offset="16" filename="DISK" physical_partition_number="0" size_in_bytes="4" start_sector="NUM_DISC_SECTORS-1." value="CRC32(NM_DISK_SECTORS-1.,92)" what="Update"/></data>)
But then still continues in the bootloop...

Phone Not Entering DA mode.

So Here are the steps
1. My bootloader got unlocked.
2. I Installed factory preloader and lk images.
3. Rebooted to Fasboot and flashed TWRP 3.3.1-0924 by wzsx150 (the only Android 9 recovery that didn't get removed immediately after flashing and rebooting for 1st time to get to recovery).
4. Formatted Data, Closed AVB 2.0 and Signed TWRP.
5. Rebooted to Fastboot and flashed stock EEA Android 9 (11.0.3.0) from Global (11.0.6.0) and reflashed factory preloader and lk.
6. Rebooted to recovery, Formatted Data, Closed AVB 2.0 and Signed TWRP.
7. Using ADB sideload from Twrp Installed EEA Android 10 (11.0.2.0).
8. Rebooted into fastboot Installed Updated TWRP-3.3.1-1210 (by wzsx150).
9. Rebooted into fastboot and flashed misc.bin from same zip (according to bat file inside it should get flashed after recovery but I forgot.)
10. BRICKED. Booted to Redmi logo for 3 seconds and rebooted infinitely.
This type of brick in 4pda.ru according to google translate can be mitigated by letting battery drain and then enter DA download mode using SP Flash Tool.
I've Used the tool several time so I thought Okay no big deal.
So This is what I tried:
11. Pressed download button
12. Connected USB Cable to phone.
13. Device pauses a second (Probably for SP Flash Tool to respond) then doesn't enter DA (Unlike previous times) and screen brighten for a second or two but then turns off and repeats this process forever.
I've been using Drivers provided by Microsoft Update Catalogue but tried all the drivers on 'MTK Usb Driver v1.0.8' and 'Mediatek_Driver_Auto_Installer_1.1352.00' after disabling Driver Signature Enforcement. but even though drivers are installed they don't get loaded and after force installing them in add legacy drivers they are their but have yellow triangles and their Location lists as 'Unknown' and status as 'This device cannot start. (Code 10)'. Tried Removing them after adding them as a site suggested but that didn't work either.

I learned the hard way to never mismatch partitions with this phone. I thought having the factory preloader and lk1/2 would protect me but no.
When you say brick, do you mean you have a completely black screen with only the notification LED turning on when you plug it in?
Grab a bootable Linux image and use that on a USB stick to eliminate the driver issue you're having. Interface is identical

wang1chung said:
I learned the hard way to never mismatch partitions with this phone. I thought having the factory preloader and lk1/2 would protect me but no.
When you say brick, do you mean you have a completely black screen with only the notification LED turning on when you plug it in?
Grab a bootable Linux image and use that on a USB stick to eliminate the driver issue you're having. Interface is identical
Click to expand...
Click to collapse
So I tried Ubuntu. Problem isn't from Drivers. It's because my Windows or linux didn't ever got a chance to enter fastboot so they can load preload drivers properly.
In Windows, Mediatek USB Port is the only driver that get loaded, and that for only an instant then it disappears in Device Manager.
In Linux according to this Tutorial everything is fine but SP Flash Tool gives me a " ERROR : STATUS_ERR (-1073676287) , MSP ERROE CODE : 0x00. "
Based on this chinese site I should find my Vendor Id and Product Id specific to my system (or is it my chipset?) and then change some files but how do I get linux to recognize mediatek usb device first when It needs to enter fastboot for that to happen.
Is there any way to manually add it?
EDIT: So After some reading I realized that I have to get my phone to fastboot first to get the drivers recognized. In windows as far as I know there is no way for manually adding 'Location' to Drivers. what about Linux?

I think you're talking about a soft-brick and I'm talking about a hard-brick. If you can get to fastboot, it's a soft-brick.
Hold the volume down and power buttons simultaneously for 1min and see if your screen changes.
Don't worry about the Linux drivers, if your phone is in the correct mode, it'll work.

I don't think it's a Soft-Brick (unless Hard-Brick means even the display not turning up at all), Holding them for a minute with battery charged doesn't do anything. As soon as it boots back up it starts getting caught in Booting until Redmi logo and staying there for 2-3 seconds then reboots. I tried to hold Volume Down + Power for 3 minutes while caught in this bootloop but no fastboot. I'll retry when battery discharges again. first without usb cable attached then with.
Thanks for taking time to work this through with me. Nowadays with all service centers being closed it's really a nightmare to have something you need on internal storage and not being able to access it. First thing I'll do after this is to buy a 128GB SD card to store the important stuff.
By the way should I just use the Live Ubuntu or Install it to see if the problem is from being a live image.

When I hard bricked my phone, I didn't have anything but that white led when I plugged it in. If you have the redmi logo, should mean there is hope. I've only ever entered DA mode when I had a hard brick.
This might be one of those situations where letting the battery drop to 0% would allow you to access fastboot. MiFlash only works in fastboot and DA mode I believe. What happens when you hold volume up and power for a minute while plugged in to your computer? Run "ADB devices" to start the adb service first
I doubt it would make a difference live to installed, but it's your call if you have the time.

With Phone in Bootloop mode Holding Either Vl+ and Power or Vl- and Power doesn't make a difference.
With Phone Off and USB detached It's the same.
With USB attached Vol+ and Power for over 3 Mins result in Device Manger listing 'Mediatek USB Port' for as long as display remains 'dark but bright' (for 2-3 seconds then shuts down and turns itself back on). removing it when phone suddenly shuts down. when USB is detached phone remains shutdown.
With USB attached Vol- and Power for over 3 Mins result in Phone's Display Brightening for 5 seconds no device listing in Device Manager nor entering fastboot or being recognized by adb or fastboot (set on a permanent re-checking by a cmd script). then phone shuts itself down and back on.
LED situation:
With Vol+ and Power with USB attached LED when phone is Off is Fullbright. When Display Brightens It turns off.
With Vol- and Power with USB attached LED when Phone is Off Blinks Once Fullbright and then remains Semi-bright whether phone is on until shutdown and the Blinks Fullbright again.

I Live in Iran and with sanctions there is no way to pay anyone overseas. Unless they're willing to risk accepting cryptocurrencies from an Iranian , my only chance if I can't work it out is to wait till unofficial service centers here open.

Your phone only being detected for 5 seconds is supposed to happen. It checks for a signal from so flash and if it doesn't see it, drops off.
I'm not sure paying someone to remotely flash your phone will work if SP Flash isn't even trying or detecting your phone. With mine, it would detect and try to flash (red bar sitting at 100%) before throwing an error.
Try letting your battery die, if that doesn't work, maybe the test point mod will work. Otherwise, I think your only option is a service center.