No flashing LED on EDL Mode - Xiaomi Redmi Note 3 Questions & Answers

My RN3 no longer shows flashing / blinking red LED while on EDL mode. Can someone help?
I'm currently on MIUI 8 6.6.23 from xiaomi.eu. Tried to fastboot flash to global dev ROM to clean flash a custom ROM, then I noticed this.
Not really an issue tho because the EDL mode works as usual. My only concern is if I decide to sell this phone later and my future customer notice this. That'd be painful to describe because I really don't know why

Related

[Unbrick Help] BQ Aquaris X5

Hello there,
i need help with unbricking my Bq Aquaris X5 Cm Edition (codenname: paella).
I flashed Twrp, was not able to flash SU.zip. And flahsing LineageOs failed with "error7"
after i was unable to flash lineage and doing other stuff i had no system installed any more so i flashed cm unnofical gohan version with the flashall.bat.
And then i rebooted and had the mess. The phone does not want to turn on. Only thing that the phones give me as a "sign of life" is the red LED when i plug in the charging cable and give him power.
Im not able to get into fastboot or recovery mode. So my questions is: Is there ANY way to get that phone back to life?
Istn the normal way flahsing old bootloader and then original firmware?
But for that i need to get to fastboot mode which im not reaching.
LaCereb said:
Hello there,
i need help with unbricking my Bq Aquaris X5 Cm Edition (codenname: paella).
I flashed Twrp, was not able to flash SU.zip. And flahsing LineageOs failed with "error7"
after i was unable to flash lineage and doing other stuff i had no system installed any more so i flashed cm unnofical gohan version with the flashall.bat.
And then i rebooted and had the mess. The phone does not want to turn on. Only thing that the phones give me as a "sign of life" is the red LED when i plug in the charging cable and give him power.
Im not able to get into fastboot or recovery mode. So my questions is: Is there ANY way to get that phone back to life?
Istn the normal way flahsing old bootloader and then original firmware?
But for that i need to get to fastboot mode which im not reaching.
Click to expand...
Click to collapse
I'm in the same situation with a BQ X5 plus, I think the only way is to get the phone to the BQ service center
Did you get the phone working again ?
Nope i handed it over to the support and got a New one because guarentee was still valid
LaCereb said:
Hello there,
i need help with unbricking my Bq Aquaris X5 Cm Edition (codenname: paella).
I flashed Twrp, was not able to flash SU.zip. And flahsing LineageOs failed with "error7"
after i was unable to flash lineage and doing other stuff i had no system installed any more so i flashed cm unnofical gohan version with the flashall.bat.
And then i rebooted and had the mess. The phone does not want to turn on. Only thing that the phones give me as a "sign of life" is the red LED when i plug in the charging cable and give him power.
Im not able to get into fastboot or recovery mode. So my questions is: Is there ANY way to get that phone back to life?
Istn the normal way flahsing old bootloader and then original firmware?
But for that i need to get to fastboot mode which im not reaching.
Click to expand...
Click to collapse
yes you have to install qualcomm drivers and see in what mode the phone are.
9006, 900E or 9008
solved
I HAD the same problem with my BQ Aquaris X Pro.
Running the lineage OS 15.1, rooted with AddonSu installed.
This is how I was able to wake it up again.
1) I unplugged the phone from the USB loading cable
(don't know if this step is needed - the battery was definitely not totally empty, when this red flashing LED thing occurred. However, i don't think the phone charges when the LED red light flashes.).
2) I took the sim card out (don't know if this step is needed).
3) I pressed for about 2 [minute] power and volume (don't know if up or down) button together. And then it woke up again.
Maybe this is the special boot recovery mode option mentioned here?
What ever it is, it worked for me.
+ https : / / wiki.lineageos.org/devices/bardockpro
Good luck!
ElmBeech

Redmi 3 Pro stuck/bootloop hopeless

R3 Pro (3GB/32GB, 2015817 version) came with some chinese/sellers custom ROM (and locked bootloader). It was heavy and bloated, so I decided to update it. Tried latest global stable (fastboot) ROM via miflash, flash was successful but that's was a lie - it stuck on mi logo...
Then I tried various other ROMs, global and developers, latest and older, some xiaomi.eu, manhit, etc. (for locked bootloader) and all I've got was either just a mi logo or mi logo with "powered by android" animation beneth. I left it for hours after flash and still nothing.
Then I found some ways to flash twrp, did that successfully, booted into it, wonder around in terminal and file manager, tried some recovery ROMs - but the result is the same - just logo or logo + animation.
I can get into fastboot (but it doesn't realy matters since bootloader is locked), download (EDL) mode, that Xiaomi menu (with Power and Vol+, with "shortcuts" to all the modes, hardware tests - btw. everything works there, etc.), twrp, charge battery (with some ROMs phone just gets warm and I know it's charging, there are no LED and/or animation, but in some everything works just like it should), but just can't boot into OS.
And I'm going nuts!
Here are some logs from the last ROM (i don't even know anymore which one is it) - pastebin.com/qaKVzxue and pastebin.com/dM3nEVj0
I'm not so experienced in looking at that but seems like every other thing in there, like cpu, i2c (touch/sensor), sound, battery, etc. is broken/faulty which is not true - everything was fine before update, and everything IS still fine according to inbuilt (xiaomi) hardware tests.
So somehow it seems that all the ido ROMs I tried are wrong for this device? Or am I missing something (quite possibly, I'm tired and pissed off)
Last night I did a backup of efs/nvram and then wiped internal memory/partitions, flashed latest global ROM, restored efs/nvram - phone stuck, but this time not on MI logo but freakin' penguin logo (like here en.miui.com/thread-377870-1-1.html). Same logo is for fastboot mode, no more bunny. Then flashed twrp and phone now shows mi logo with "powered by android" animation beneath, like before...
I don't know how this works with Xiaomi phones, but looks like it worked with some factory/seller special combination of ROM and bootloader. Then I did update and something stuck, maybe differences between ROM and bootloader, or some inside/hidden security mechanism that stops boot process? And because I can't find original firmware and/or bootloader is locked (maybe even updated?) it's now stuck...
Either that or some HW fault, but it would be insane that official ROM update with official tools and in factory download mode with full battery can cause such problem!
Can you go to twrp recovery?
Yes, like I said in the first post. I can do anything but boot android/MIUI. It's either because of locked bootloader or somehow official ROM installed officialy (via MiFlash in EDL mode) bricked phone, which is catastrophic bug i.e. epic design/implementation fail by Xiaomi.
Try this
https://forum.xda-developers.com/redmi-3/help/bootloop-bootloader-locked-options-t3331139
Sorry to intrude, I have pretty much the same problem.
Phone is stuck in bootloop and I can only access fastboot mode and EDL mode (but in EDL the phone does not connect to pc) and when I try to flash a stock ROM (since I know it is a software issue due to an unfortunate update) it says "locked device". So I tried to unlock it via MiUnlock... but phone cannot be verified 'cause "account not bound to this device" and obviously I cannot change any options since I cannot use my phone.
Please, help
it was happened to me about 3 days ago when i play around with the twrp & rooting thingy... tried everything from youtube to various forum solutions... just one link really works when you only have fastboot options and your phone bootloader is still unlocked. just follow the steps in the OP... key things here is downloading the tool to read your phone as mentioned in the OP i.e [TOOL]Minimal ADB and Fastboot [1-6-17]
1) Download Tool -> https://forum.xda-developers.com/showthread.php?t=2317790
2) Follow all the steps in the OP -> http://en.miui.com/thread-277276-1-1.html
3) Enjoy your phone from back from the dead.. LOL!
4) Remember here, the key is NEVER GIVE UP and PATIENT!
NOTE : The Device will start, wait till completion , it can take up to 10 Minutes. -> for me around 15-20 minutes for I have flashed the current beta rom of MIUI8 7.6.8
cheers, guys!
blx-
I had a similar situation.
Officially unlocked boot loader. Flashed TWRP using fastboot. Only got the mi logo and a boot loop on start up.
Could not turn on. Could not boot into TWRP.
When the phone was boot looping I could still get into fastboot mode by holding power+volume down.
I booted from fastboot mode into TWRP by opening the command prompts and using
"fastboot boot twrp2.img"
That got the phone available from windows explorer. I was able to move a new ROM image to the SD card and install from TWRP.
Currently running lineage 14.1 -20190112.
I lost a bunch of **** but my phone seems to turn on for the moment.
Note, I still cannot boot into TWRP using the phone only. I can only boot in from fast boot as above.

HELP: Screen replacement and phone stuck at Mi logo

I replaced the broken screen on my Kenzo and now it's stuck at the Mi logo. Funny thing is the technician said when he disconnects the touch ribbon it boots normally (but obviously with no touch) and locks up with Mi logo when it's connected. I've read that the mtk and sd screens are interchangeable so I don't think that's the issue. I don't have access to another screen so I have to make do with this one anyway.
I bought the phone from Gearbest two years ago and it came with the vendor rom which I never changed. I'm suspecting the vendor rom has something to do with it and now is the perfect time to flash a new rom before I sell it. Only problem is I have no clue how to flash a rom. I can get it to the fastboot screen but that's it.
Could someone please help me but in plain laymans English? Flashing for Dummies kind of thing. I've been a member here a while but haven't grasped the lingo or their meanings yet.
Thanks in advance.
Hooow?! said:
Google miflash
And download it.
Also download the latest miui developer rom
http://bigota.d.miui.com/8.1.25/miui_HMNote3ProGlobal_8.1.25_16348801ef_6.0.zip
Search for EDL.zip from xda itself and follow the instructions to get to edl mode from fastboot mode( to see if it's in edl mode check for the red blinking status LED when connected to the pc)
Now open miflash as administrator connect your phone to the PC.
Miflash should see it as something like COM..
Now extract the developer rom and in miflash browse for the extracted direvtory
At the bottom right select clean_all lock.bat and then press flash..
After few minutes the flashing should get completed and then hold the power button on the phone until u see the mi logo.
Wait for the booting to get completed and then setup the phone..
Congratulations you bow have a working phone again.
Click to expand...
Click to collapse
Thanks for the help. Well I got it all the way to flash in edl and around 9% it gave an error message "Object reference not set to an instance of an object" or something similar. So it basically failed. What can I do? I'm almost there
Hooow?! said:
Google some fastboot commands to erase partitions...
It should be something like this
fastboot erase boot
fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
First go to fastboot mode by holding vol down and power together .
Then connect to PC and then install minimal adb and fastboot kit. Then open the shortcut in desktop and then type fastboot devices and check if u device is there or not. If yes then copy and paste the commands above and then repeat the EDL flash procedure.
Click to expand...
Click to collapse
This is depressing. I followed your instructions and used the command "fastboot format partition" as that's the only one that would work and was suggested in options. The result was "failed device locked". :crying::crying::crying:
Yep. Same result. Does the bootloader have anything to do with all this?
Any ideas why it would boot normally with the touch ribbon disconnected but bootloop when connected? I'm beginning to wonder if flashing will even work.
WELL!! My phone is suddenly working. After trying all sorts of flashing methods I put it on the charger this morning and just took it off and it's working perfectly.
What happened was I read another thread about flashing the Global rom with a locked bootloader. At the very end of the instructions and almost as an after thought, the author mentioned that you must boot the phone into recovery in order to clear the cache etc otherwise the phone will be stuck on the Mi logo. It sounded similar to my problem so I did volume up and power key together and the Mi logo came up. Thinking nothing had changed I did volume down and power and went into fastboot. Again nothing changed. So I switched it off, put it on the charger and left it for about 4 hours. I just took it off the charger 20 minutes ago and it was working perfectly.
Perhaps someone can explain what the heck happened? Meanwhile I'm selling it pronto. Lol
Twotems said:
WELL!! My phone is suddenly working. After trying all sorts of flashing methods I put it on the charger this morning and just took it off and it's working perfectly.
What happened was I read another thread about flashing the Global rom with a locked bootloader. At the very end of the instructions and almost as an after thought, the author mentioned that you must boot the phone into recovery in order to clear the cache etc otherwise the phone will be stuck on the Mi logo. It sounded similar to my problem so I did volume up and power key together and the Mi logo came up. Thinking nothing had changed I did volume down and power and went into fastboot. Again nothing changed. So I switched it off, put it on the charger and left it for about 4 hours. I just took it off the charger 20 minutes ago and it was working perfectly.
Perhaps someone can explain what the heck happened? Meanwhile I'm selling it pronto. Lol
Click to expand...
Click to collapse
Just dont sell it yet use some awesome oreo roms best is u try resurrection remix oreo its the best with agni kernel and enjoy..... Dont sell the kenzo man just enjoy the roms u can unlock bootloader unofficially which is far better and easier than official one and then flash twrp enjoy the phone
Androbots said:
Just dont sell it yet use some awesome oreo roms best is u try resurrection remix oreo its the best with agni kernel and enjoy..... Dont sell the kenzo man just enjoy the roms u can unlock bootloader unofficially which is far better and easier than official one and then flash twrp enjoy the phone
Click to expand...
Click to collapse
Lol. Nah, I already have a Mi Mix 2 which I'm loving. This old faithful has to go.

Bricked phone, i need your help.

Hello,
Today i flashed a twrp to my phone infinix hot 3 x553 (snapdragon 415) but by mistake i found that it was a custom recovery for another phone, what a mistake!!
When i start the phone, i got only a blank screen with some grey lines, i tried to get into DL mode but no way so i cant flash the stock rom using QFIL, i can only go to fastboot mode which is not a good thing. I found some solution in other forums that let Xiaomi users to go from fastboot to edl mode but it doesn't work for my phone.
I hope that what the phone have isn't a hard brick.
Please i need your creative solutions.
Thank you a lot !

Redmi Note 9 Pro bricked after flashing with Mi flash Tool

Hi Guys, so the things I was using the official AOSP extended rom on my Redmi Note 9 Pro after but after ccouple of days changed my mind wanted to revert back to the official MiUi rom. So used the Miflash Tool to flash "joyeuse_global_images_V12.5.4.0.RJZMIXM_20220215.0000.00_11.0_global" after flashing it reported a failed error and the fastboot screen started flashing on and off. After turning off the phone and pressing the power button to turn the phone flashes the redmi logo for less than a second and turns off. Plugging in the charger makes the phone flash Redmi logo and then turn off again repeatedly. I can neither get into fastboot mode nor into recovery. Is there any solution to this problem? Any help will be much appreciated. Below is a short clip of the problem.
Abir172 said:
Hi Guys, so the things I was using the official AOSP extended rom on my Redmi Note 9 Pro after but after ccouple of days changed my mind wanted to revert back to the official MiUi rom. So used the Miflash Tool to flash "joyeuse_global_images_V12.5.4.0.RJZMIXM_20220215.0000.00_11.0_global" after flashing it reported a failed error and the fastboot screen started flashing on and off. After turning off the phone and pressing the power button to turn the phone flashes the redmi logo for less than a second and turns off. Plugging in the charger makes the phone flash Redmi logo and then turn off again repeatedly. I can neither get into fastboot mode nor into recovery. Is there any solution to this problem? Any help will be much appreciated. Below is a short clip of the problem.
Click to expand...
Click to collapse
Can you post the log of Miflash?
Here's the log of the flash.
NOSS8 said:
Can you post the log of Miflash?
Click to expand...
Click to collapse
According to the log, the flash was successful, the error is normal (6:02:45 PM 9f886790]:error:Not catch
checkpoint (\$fastboot -s .* lock),flash is not done) since you did not lock the bootloader (flash_all.bat).
After the flash the phone reboots automatically, did you interrupt it?
First try to see if a button is not defective, a bit of WD40 product for example and operate it several times.
But if it worked well before it would be a strange coincidence but it is possible.
(I had this case on one of my phones by dint of flashing).
Hi sir I have this problem too
elinajafi said:
Hi sir I have this problem too
Click to expand...
Click to collapse
Can you post the log of Miflash?
It seems like a common issue happens with me when I try to flash stock rom via fastboot, if you ever been able to enter fastboot flash custom recovery (like twrp) and use it to flash the stock rom zip (recovery method), it should work..

Categories

Resources