Hi guys,
I have a Redmi Note 4 (MTK, 3GB RAM/64GB)
Have been using the global stable ROM without issue for about 3-4 months. No custom recovery, root, etc.
Yesterday, I used the phone till the battery completely discharged. I then tried to charge it back up, but it wouldn't boot:
- On normal boot, I see the Mi logo (but not the "powered by Android" one), which then disappears shortly to leave the backlight LEDs switched on, but nil graphics
- I get the same result if I try to boot into recovery (vol up & power)
- Am able to boot into FastBoot without issue
Have tried to flash the China Dev, China Stable & Global Stable Roms using SP Flash 5.1632 (used methods outlined in http://en.miui.com/thread-371349-1-1.html & http://en.miui.com/thread-370620-1-1.html) but to no avail. The flashing process goes through successfully, but the boot failure still persists.
Any ideas anyone? Thanks in advance!
So....managed to work this out
I left the device overnight to discharge completely (with the screen's LED backlights still on)
charged it to full without switching on the device and voila, back to life
hope this helps anyone out there with the same issues
Related
Device: Galaxy Player 5.0 INTL (YP-G70)
ROM: Cyanogenmod 10.1 (7/23/2013)
Kernel: Sultan r5 INTL
Problem: The battery appears to be malfunctioning somehow. After using "Pimp My Rom" and enabling some tweaks, the device began to randomly turn off and loop on and off with a white battery outline onscreen. Now, the battery has sufficient charge. When it finally turns on, it's always over seventy percent. When it does turn on, if it is plugged in on the wall charger, it immediately turns off upon disconnecting this wall charger. Also, it displays "Android is upgrading, starting apps" at every boot. Managing to turn on the device after doing a reboot with the power button many times takes up to 15 minutes. It sucks. ):
Steps attempted:
Reflashing ROM and kernel using exact steps (wiping all data, /system, cache, etc.).
Flashing Cyanogenmod 10.2 (8/05/2013) with Sultan r6.
Deleting battery stats.
Cleaning charger and microUSB port.
Rechanging tweaks to the values I remember in Pimp My Rom. (IDK about all of them, if someone could post the defaults that would be great).
Draining battery (I did to 1%) and then recharging. Should I drain until it turns off?
[EDIT]: Tried flashing to Chip v1.5 with r14 kernel. No luck; it is just a different battery icon.
[EDIT]: Tried flashing to stock with Odin.
Are there any steps that I could possibly take to fix this? Perhaps flash to stock and see if the problem persists?
[WORKAROUND!] I've found a workaround, however annoying it may be. Plug in the YP-G70 and it should bootloop with the battery icon. However, as the icon disappears and the screen is black for about a second, just before it is about to reboot with the icon, pull the charger from the device. This has guaranteed my device to start every time; I can't ensure that it will work for you, but it is worth a try.
Please help!
You need to either do a factory reset from within the settings or wiping factory reset from within CWM. If that doesn't work you may need to flash back to stock.
Sent from my YP-G1 using xda app-developers app
obscuresword said:
You need to either do a factory reset from within the settings or wiping factory reset from within CWM. If that doesn't work you may need to flash back to stock.
Click to expand...
Click to collapse
I have done many factory resets from CWM. Would flashing back to stock do anything that flashing another rom wouldn't?
Also, after scouring xda for answers, I saw iurnait recommended draining the battery until the device turns off. I'm going to try that I suppose.
I'd flash back to stock if that doesn't work
Sent from my YP-G1 using xda app-developers app
Unfortunately, flashing to stock using Odin didn't remove the problem.
I used a guide from androidromupdate
To be honest, I've given up. I'll update the original post with what I've tried and the workaround that I've found for this dreadful issue. If anyone else has this issue, best of luck!
I've got the same "boot loop with battery logo" problem, but without the random shutdowns are "android is upgrading" message on boot.
Some additional details:
I can boot into download mode without any trouble.
It will occasionally complete a boot, but gets stuck in the loop as soon as something causes it to reboot or shutdown.
I can sometimes boot into recovery mode. It will successfully go into recovery mode about 2-3 times before it will go into a normal boot.
Flashing alternate kernels (even going all the way back to stock) just changes the battery logo, but does not stop the bootlooping problem
The stock kernel was far more reliable than the others, often booting all the way after only 3 or 4 tries.
Throughout the boot loop, the battery logo (except in the stock kernel) will show as empty, even after being charged overnight
Upon a successful boot (all the way to android home screen), the battery is shown as fully charged (if it's been charging) or a level that seems probable (e.g. it'll show as 70-80% if it's been in download mode (which keeps screen on at full brightness) for a while or left to bootloop for close to an hour.
If it's not plugged into a charger, it only loops once each time you turn it on (i.e. battery logo shows for a few seconds then the device shuts itself off).
An update to Joseph's posted workaround:
I've found the button lights a perfect indicator for the timing. Wait for them to go black and then come back on very dimly then unplug the cable before the screen shows anything or the key lights go full brightness (like they are when device is fully booted and awake).
Hi i just bought a redmi note 3 sd version and i unlocked it officially, installed Alka recovery, and when i install MIUI based Rom or the official one. My phone boots normally but when i try to reboot my device, the device keeps showing Mi logo and it reboots to Mi logo again and again and again....till battery dies. Tried installing AOSP or CM13 but it looks im the only person that has a problem with fingerprint in both ROMs.
Pleasee helpppp.
Sent from my Redmi Note 3 using Tapatalk
Hey, what kind of problem do you have with fingerprint compatible ROM?
Because I have problem with fingerprint compatible ROM too (always stuck in Mi Logo after flash)
And when I flash MIUI (Official or ROM based) it always reboot randomly, but random reboot always happen every 5-10 seconds phone booted up, it also happen in AOSP 5.1.1
This phone is driving me crazy
I can't use almost every single ROM
- MIUI & AOSP (random reboot)
- CM13 with fingerprint compatible (can't booted up / stuck in mi logo) and then can't enter recovery until it to re-unlocked and reflash TWRP again to able enter recovery
The only ROM I can use are CM12.1 and CM13 with fingerprint uncompatible, it can booted up normally (maybe because the bootloader still not relocked) but the battery drain like crazy
Android OS/System used battery usage more than SOT
Wonder someone can fix the problem
putrairlangga said:
Hey, what kind of problem do you have with fingerprint compatible ROM?
Because I have problem with fingerprint compatible ROM too (always stuck in Mi Logo after flash)
And when I flash MIUI (Official or ROM based) it always reboot randomly, but random reboot always happen every 5-10 seconds phone booted up, it also happen in AOSP 5.1.1
This phone is driving me crazy
I can't use almost every single ROM
- MIUI & AOSP (random reboot)
- CM13 with fingerprint compatible (can't booted up / stuck in mi logo) and then can't enter recovery until it to re-unlocked and reflash TWRP again to able enter recovery
The only ROM I can use are CM12.1 and CM13 with fingerprint uncompatible, it can booted up normally (maybe because the bootloader still not relocked) but the battery drain like crazy
Android OS/System used battery usage more than SOT
Wonder someone can fix the problem
Click to expand...
Click to collapse
Today i will try installing ROM with fastboot and delete twrp,supersu everything and relock bootloader and then i will try everything from the begining.
And i want to try the new Flyme Os because it has fingerprint scanner working.
Sent from my Redmi Note 3 using Tapatalk
putrairlangga said:
Hey, what kind of problem do you have with fingerprint compatible ROM?
Because I have problem with fingerprint compatible ROM too (always stuck in Mi Logo after flash)
And when I flash MIUI (Official or ROM based) it always reboot randomly, but random reboot always happen every 5-10 seconds phone booted up, it also happen in AOSP 5.1.1
This phone is driving me crazy
I can't use almost every single ROM
- MIUI & AOSP (random reboot)
- CM13 with fingerprint compatible (can't booted up / stuck in mi logo) and then can't enter recovery until it to re-unlocked and reflash TWRP again to able enter recovery
The only ROM I can use are CM12.1 and CM13 with fingerprint uncompatible, it can booted up normally (maybe because the bootloader still not relocked) but the battery drain like crazy
Android OS/System used battery usage more than SOT
Wonder someone can fix the problem
Click to expand...
Click to collapse
I tried everything but i still get the bootloop problem so Im gona install chinese developer ROM with MiFlash and im not gonna root or install anything :,(
Handset: Xiaomi Redmi 3 Pro.
Steps done:
1. bought on aliexpress with some suspicious bloatware preloaded.
2. was unsure if bootloader is locked, so flashed modified bootloader and TWRP as per this guide: http://en.miui.com/thread-276565-1-1.html
3. flashed latest xiaomi.eu dev build: xiaomi.eu_multi_ido_6.5.26_v7-5.1
4. boot, reboot
5. flash SuperSU via TWRP: UPDATE-SuperSU-v2.65-20151226141550.zip
6. booted and used several days, few reboots. All working fine, except apps closing in background and bluetooth earpiece losing connection. Described here: http://forum.xda-developers.com/redmi-3/help/redmi-3-pro-impressions-closing-t3397186
Where problems have started:
7. Decided to get stable xiaomi.eu release. Maybe forceclose and BT issues are resolved?
8. booted to TWRP and flashed STABLE release from xiaomi.eu: xiaomi.eu_multi_ido_V7.3.1.0.LHPCNDD_v7-5.1.zip
9. also flashed SuperSU without restart: UPDATE-SuperSU-v2.65-20151226141550.zip
10. After restart, I get boot loop.
It does very short boot attemps: when powered on, it vibrates and displays MI logo for a second, then reboots. Repeats it quickly 2 or 3 times and switches off.
Unable to go in to download mode, as volUp + Pwr will also give bootloop.
VolDn+Pwr will load fastboot after one reboot. MiFlash utility finds the phone, but throws an error on flash attempt (file not found or something).
If restarted with all VolDn+VolUp+Pwr buttons pressed, it will not turn on the screen at all, but appears on MiFlash utility and I am able to flash it. But still bootloops after that.
If I flash it with original bootloader, not the modified one as per guide (on step 2), I am able to boot in to china MIUI, and also in to bootloader menu. But of course TWRP does not work.
How do I do it with locked bootloader:
1. flash TWRP?
2. flash stable xiaomi.eu release?
3. get root?
Of course all of this is needed only until stable CM comes out.
Also, if bootloader is unlocked, is it displayed somehow? For example my old motorola would show a nasty warning during boot.
Short update. I have managed to install the latest xiaomi.eu ROM.
Unmodified bootloader is needed.
Flash TWRP via MiFlash separately, after MIUI is installed and booted.
Then flash SuperSU and you're good.
EDIT: I lost all my data since the phone was encrypted, but I recovered it flashing in fastboot mode
My Redmi 3 pro is stuck in a bootloader after trying to root it for the first time.
power off doesn't do anything.
power and volume up doesn't do anything
power and volume down shows a Fastboot logo with a cartoon, but I don't know what to do here and if it is useful.
After 1-2 minutes in fastboot logo it starts again in bootloop.
I've tried to press both volume up and down and power and keep it pressed for several bootloop cycles. It looks like the phone switched off, or at least the screen was black.
After restarting it again bootloop
I think soon the battery will drain and the phone switch off
I really don't know what to do
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.
hello everyone,
my redmi note 3 pro special (kate) with locked bootloader and always original roms (never modified) has been stopped for about 2 years due to inactivity, but before it had always worked great!
wednesday I tried to turn on my kate.
the device went into continuous bootloop. whereupon I tried to enter fastboot, activate edl and flash with miflash a whole series of roms, from the last, to 9.6, 9.5, 6.7 and all those that can still be found, but always with the same disappointing result: the device makes the first start (sometimes forcing it with a restart because it remained enchanted for hours in the initial animation after the "mi" logo), but immediately during the initial configuration of the so returns to restart without allowing use.
whereupon, I decide to open the back of the redmi and disconnect the battery overnight, in the hope that this could solve any problems.
but unfortunately nothing...
after yet another flash and I start, I can't even start this morning: when I press the power button the fixed initial logo "mi" starts, goes off and starts again ... I'm practically in infinite bootloop ...
I only need the kate as a forklift, but I would be sorry to have to throw it away completely.
does anyone have a suggestion to get out of this troubles?
kletius said:
hello everyone,
my redmi note 3 pro special (kate) with locked bootloader and always original roms (never modified) has been stopped for about 2 years due to inactivity, but before it had always worked great!
wednesday I tried to turn on my kate.
the device went into continuous bootloop. whereupon I tried to enter fastboot, activate edl and flash with miflash a whole series of roms, from the last, to 9.6, 9.5, 6.7 and all those that can still be found, but always with the same disappointing result: the device makes the first start (sometimes forcing it with a restart because it remained enchanted for hours in the initial animation after the "mi" logo), but immediately during the initial configuration of the so returns to restart without allowing use.
whereupon, I decide to open the back of the redmi and disconnect the battery overnight, in the hope that this could solve any problems.
but unfortunately nothing...
after yet another flash and I start, I can't even start this morning: when I press the power button the fixed initial logo "mi" starts, goes off and starts again ... I'm practically in infinite bootloop ...
I only need the kate as a forklift, but I would be sorry to have to throw it away completely.
does anyone have a suggestion to get out of this troubles?
Click to expand...
Click to collapse
Factory reset
Black_Stark said:
Factory reset
Click to expand...
Click to collapse
I've tried several times... but... nothing
kletius said:
I've tried several times... but... nothing
Click to expand...
Click to collapse
Did u replace any component at repair shop?
Black_Stark said:
Did u replace any component at repair shop?
Click to expand...
Click to collapse
I've tried factory reset, flashing several roms, unmount the battery... now the phone Is witouth battery, i want to try keep witouth Energy a few days ...