Hello!
My device has been struck at EDL mode for the past 5 days without recover.
I tried that 'guide' where we wait for the device to discharge, got to the point where the battery icon appears, but the device still refused to boot.
Does anyone now something else I could try? I want to avoid opening the device if possible, unless there is no other choice.
Does anyone have or know someone that has a Mi account with authorization for EDL flashing?
Related
Hello,
my friend has a problem with his phone. He neither installed a custom rom, nor he rooted it. He updated OTA and after a week, while he was talking, the phone shut down.
When he powers it on the screen lights up and nothing else happens. Sometimes the vodafone splash came up, but nothing more.
I don't know if the phone boots into recovery as I don't see anything on the screen.
I tried booting to fastboot mode, and the pc detects it. But I whatever I try to do, (flash,erase etc) I get the error: Remote not allowed...
Any ideas how to fix it?
Have you considered hardware problem?
Yes I have but first i want to make sure that it isn't any software problem
my p10 plus got got bricked and it is always going to eRecovery without going to home screen after update. my phone is BOOTLOADER LOCK, NOT ROOTED THOUGH. and i want to fix this . i need help . ps : i hope theres a method that could fix this without unlocking bootloader.
mongs said:
my p10 plus got got bricked and it is always going to eRecovery without going to home screen after update. my phone is BOOTLOADER LOCK, NOT ROOTED THOUGH. and i want to fix this . i need help . ps : i hope theres a method that could fix this without unlocking bootloader.
Click to expand...
Click to collapse
hi, do you dolve your problme? i guess i have the same problem XD
regards
My P10 plus started this exact problem today. Always stock, never rooted or boot unlocked.
I was playing a game and it rebooted. Started again and lasted a minute but then constant bootloop to eRecovery screen.
Did the erecovery image download and didn't do anything brought me back to the same screen
Tried to factory reset on the ecovery screen and then booted, but during setup it rebooted.
Went to fastboot screen (pwr+vol down while attached to usb) and rebooted after. I was able to go through setup.
After letting it for sit for only 2 minutes as I type this message, it randomly started rebooting on its own.....and now back to recovery screen.
FACKKKKKKK
UPDATE: Took my phone in to a cell repair shop after exhausting all my troubleshooting options.
They said they took the phone apart to disconnect the battery and do a full power drain. Then after reconnected they installed EMUI 9.1 again via USB and got the phone up and running.
Been working for me for the past 6 hours, but the phone just rebooted on me once, so i'm sure they're still an unsolved demon in it. but no idea what it is right now.... May be time to start phone shopping.
maybe just battery broken, install app accu battery or any other to check batery
The phone rebooted by it self, no firmwareupdate going on, just random reboot.
Got stuck on redmi logo.
Could reboot and get fastboot, but could not flash original fastboot rom, got errors. a normal reboot gave only redmi logo.
Now the phone is out of power, not taking charge, not powering on.
Anyone have any solution for this problem? Or any tips? The phone is stone dead
Not sure if this will help...
here's my random reboot thread and fix
Well, i have no simcards or sd-cards inserted.
And its not charging or turning on. volume up and down + power is not making any results.
The weird thing is that it said "redmi" on the display for about 24 hours draining the power, and after it died out of power i'm unable to do anything with it. its basically a brick.
This happened totally random. just a spontaneous reboot into a never ending redmilogo.
During redmilogo i had the posibility to get it into fastboot by rebooting it, but mi flash would not accept the phone. so another reboot into regular boot ended in infinite redmilogo again :|
Your phone's bootloader unlocked?
Nope
Did you try keeping it charged for a while? Device might not show any sign (charging indication) but the battery will get charged eventually (I guess).
Charge it well and try to SIDELOAD that FASTBOOT IMAGE via PC..
It loooks like its bricked all by itself. i left it in charger for days.
I got contact with the phone with mi flash, but it has gone into some authentication mode with the flashing, so i'm not possible to reflash rom without authorization.
Read about this on reddit, and it seems like a dealer has to look at it.
I was trying to get FRP unlocked cause I cant do it in developer options. Thinking I would fix the problem, I relocked the phone, and now it's experiencing a soft brick. When it turn it on the Huawei logo appears and dissappears, then it reboots to erecovery. Is there a way to fix this or am I SOL? I am getting real sick of this phone anyways.
TL;DR it's bootlooping, and I can't enter download mode.
My V20 H910 hasn't been touched for a couple years now. It started bootlooping years ago, and it's only now that I'm trying so hard to fix it. When I try to boot it, I get the LG screen for a few seconds, then it goes all black, and then it repeats until I pull the battery.
I can navigate to the screen to initiate a factory reset, but when I confirm, it freezes up for a moment and then goes back to the boot loop.
When I plug it in to initiate download mode, I get the screen that says it's trying to start download mode for a couple seconds, and then it goes back to the boot loop. I tried launching LGUP during this two second period, and unsurprisingly, it does not see the phone.
I've tried putting it in the freezer, and I've tried using a different battery. I tried "discharging the capacitors on the motherboard" by removing the battery and pressing the power button fifteen times. This causes it to vibrate briefly when I attempt to power it on, but then it bootloops as normal.
It's totally stock Oreo - no root, no custom ROMs, no TWRP, no unlocked bootloader. I might have enabled USB debugging, but that doesn't do me much good when it won't boot (yes, I tried ADB anyways, and no, it doesn't see it).
I did use third party USB cables to charge it back when it worked, so I am aware that this may just be a faulty motherboard. But I'm hoping there's another option I haven't pursued yet.
What do you think? Is it a brick? I've spent all day searching for potential fixes, so any help is appreciated!