MIUI Roms gets bootloop after reboot!!! - Xiaomi Redmi Note 3 Questions & Answers

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 :,(

Related

Mi logo shows very quick then everything goes black

Hey,
So I was on CM13 for a long time just updating OTA, everything worked fine.
Today I OTA:d and recieved 7.1.1 (Must be cm14) and when I booted it up after flashing new gapps my fp sensor wasnt working.
So I was doing alot of flashing, I flashed the lib files for goodix and reflashed radon a couple of times to try between the different FP settings.
After that I read that you need to flash the newest firmware for it to work, so I downloaded and flashed the firmware linked on the cm14 strix page, then flash radon on top of that. Keep in mind that I never did any clean rom installs, just installing on top of the rom the whole time.
Now when I tried booting after the new firmware stuff the mi Logo comes up less then a second, it vibrates at the same time as the logo comes up and then it just dies. Like the screen turns off. If i hold the power button for about 10 seconds the same thing happens again. I can't acces my recovery.
The only thing that happens is when I plug in my charger the led light turns red. Could someone please help me?
oggew2 said:
Hey,
So I was on CM13 for a long time just updating OTA, everything worked fine.
Today I OTA:d and recieved 7.1.1 (Must be cm14) and when I booted it up after flashing new gapps my fp sensor wasnt working.
So I was doing alot of flashing, I flashed the lib files for goodix and reflashed radon a couple of times to try between the different FP settings.
After that I read that you need to flash the newest firmware for it to work, so I downloaded and flashed the firmware linked on the cm14 strix page, then flash radon on top of that. Keep in mind that I never did any clean rom installs, just installing on top of the rom the whole time.
Now when I tried booting after the new firmware stuff the mi Logo comes up less then a second, it vibrates at the same time as the logo comes up and then it just dies. Like the screen turns off. If i hold the power button for about 10 seconds the same thing happens again. I can't acces my recovery.
The only thing that happens is when I plug in my charger the led light turns red. Could someone please help me?
Click to expand...
Click to collapse
I can get into fastboot mode too if that helps in any way
The phone says its bootloader is locked in fastboot, will I still be able to flash TWRP via fastboot?
try re-unlock the bootloader via fastboot using mi flash unlock (official unlock), then reboot after success.
hope it helps.
oggew2 said:
Hey,
So I was on CM13 for a long time just updating OTA, everything worked fine.
Today I OTA:d and recieved 7.1.1 (Must be cm14) and when I booted it up after flashing new gapps my fp sensor wasnt working.
So I was doing alot of flashing, I flashed the lib files for goodix and reflashed radon a couple of times to try between the different FP settings.
After that I read that you need to flash the newest firmware for it to work, so I downloaded and flashed the firmware linked on the cm14 strix page, then flash radon on top of that. Keep in mind that I never did any clean rom installs, just installing on top of the rom the whole time.
Now when I tried booting after the new firmware stuff the mi Logo comes up less then a second, it vibrates at the same time as the logo comes up and then it just dies. Like the screen turns off. If i hold the power button for about 10 seconds the same thing happens again. I can't acces my recovery.
The only thing that happens is when I plug in my charger the led light turns red. Could someone please help me?
Click to expand...
Click to collapse
Your bootloader is locked by firmware flashing. You need to unlock it again. Flash MIUI via EDL mode and then unlock. It'll wipe everything.
Just unlock the bootloader as you did in the first.. DO not flash the latest cm 14.1 firmware.. it relocks the bootloader.. check for modified firmware in CM14.1 thread.. it will boot without any issue... Had same issue.. using tesla now without any issue..
Try to unlock bootloader and see. If it does not help you need to flash MIUI Rom using EDL mode. I too get same problem sometime when flashing and trying various custom ROM and only method worked for me is flashing MIUI Rom again using EDL mode and than flashing other custom Rom again. All the datas will get wiped when you flash using EDL Mode. Hope it will help You.
oggew2 said:
Hey,
So I was on CM13 for a long time just updating OTA, everything worked fine.
Today I OTA:d and recieved 7.1.1 (Must be cm14) and when I booted it up after flashing new gapps my fp sensor wasnt working.
So I was doing alot of flashing, I flashed the lib files for goodix and reflashed radon a couple of times to try between the different FP settings.
After that I read that you need to flash the newest firmware for it to work, so I downloaded and flashed the firmware linked on the cm14 strix page, then flash radon on top of that. Keep in mind that I never did any clean rom installs, just installing on top of the rom the whole time.
Now when I tried booting after the new firmware stuff the mi Logo comes up less then a second, it vibrates at the same time as the logo comes up and then it just dies. Like the screen turns off. If i hold the power button for about 10 seconds the same thing happens again. I can't acces my recovery.
The only thing that happens is when I plug in my charger the led light turns red. Could someone please help me?
Click to expand...
Click to collapse
d
u bricked your device... flash fastboot rom and unlock the bootloader.

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.

Redmi Note 4 not booting despite flashing

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

Very slow boot up..

My device is a kenzo 3gb 32gb and I face extremely long boot times just because the phone is stuck on mi logo for at least 30secs before starting the os boot animation.. Also after flashing open gapps latest I lost the ability to reboot to recovery and even i cant power off my phone until I go to twrp also third party apps don't reboot the phone to recovery. (Btw i am on omni homemade 8.1 oreo with shadow kernel and reboot to recovery and power off just worked fine without gapps installed)
Can anybody suggest me a fix or workaround for these annoying things I really don't like it.
Thanks in advance.
Those are shadow kernel bugs, change your kernel.

Poco F1 stuck in boot loop but with a difference.

Hello Respected Members,
I have a POCO F1 6gb/128gb model
I was running Pixel Experience plus A11 rom
Today While using the Device it suddenly got switched of by itself.
The problem here is When i try to switch on the device while its plugged in then it'll start but as a soon as i remove the Charger it switches off and goes into boot loop.
I thought its a batter problem but it seems that its not the case of battery because when i put it in Recovery mode it'll stay there of hrs but as soon as i try to boot into rom it goes into bootloop.
Also bootloader is also not working as whenever i try to find the device in pc with command "fastboot devices" , The device restarts itself.
I have tried Clean Flashing Another rom , Change the Recovery , formatting the whole device including internal storage and then again flashing the Rom still no use.
I am attaching logs too.
and the recovery that is used is TWRP 3.6.0_9
If someone please help I would be very grateful
thank you
remaining logs
if you can open back of your phone try to reconnect your battery connector
CV-Aurora said:
if you can open back of your phone try to reconnect your battery connector
Click to expand...
Click to collapse
how can that help ?
any explaination ?
STUCK on boot loop
I was using the latest Lineage OS with the stock kernel for POCO F1 but after switching to Optimus drunk kernel I started facing issues where my phone would turn off automatically.
But after switching to Pixel experience, It was stuck on a boot loop I couldn't even use the recovery.
after reinstalling the recovery using bootloader, I tried installing the stock kernel and lineage again. I tried factory resetting and formatting data. but it won't start again.
PLEASE HELP me my phone won't start I tried installing everything several times.
THANK YOU!!
Ved0704 said:
STUCK on boot loop
I was using the latest Lineage OS with the stock kernel for POCO F1 but after switching to Optimus drunk kernel I started facing issues where my phone would turn off automatically.
But after switching to Pixel experience, It was stuck on a boot loop I couldn't even use the recovery.
after reinstalling the recovery using bootloader, I tried installing the stock kernel and lineage again. I tried factory resetting and formatting data. but it won't start again.
PLEASE HELP me my phone won't start I tried installing everything several times.
THANK YOU!!
Click to expand...
Click to collapse
will getting an edl flash fix this? or is there any other way?

Categories

Resources