Database Info

[Completed] [Q] Nexus 4 won’t boot up/work without charger plugged in after flashing

I have flashed a CM12 nightly using TWRP recovery. After that, during rebooting, phone switched off automatically after showing “google” logo. I went back to the TWRP and installed the backup which I have kept (stock lollipop 5.0.1). After that when I’m trying to turn on, it’s working with the charger plugged in. If I remove the charger after switching on, if I kept it idle, it will stay on till the battery is empty (I got around 24 hrs). But if I try to take mobile data or camera it will switch off for sure. Sometimes just moving across different home screens also will make it switch off. The battery status show is also not correct when switched on. In recovery mode it works well without battery and battery percentage is also correct.
What will be the reason?? Is it something related to the firmware or a Hardware issue?? Will changing the battery help??

Please Flash Stock Firmware. Once done, you can try another Nightly of CM. If it persists, please post in [Q&A] [Mako][Nexus 4][ROM][CM12][5.0.2] Temasek's UNOFFICIAL Build [v4.2 - 04/01/201
Oh Yes, Don't do any of this until the Battery is Fully Charged.

Sudden bootloop now even stock won`t flash

I`ve been usgin havoc 10.0 for the past 2 months and no problems at all until today.
Left my phone idle for some hours and when I tried to unlock it, it was off. force rebooting it took me to the rom loading screen and after 2 secs, a restart to the mi logo and then it turns off.
Tried dirty reflash of the rom with TWRP, a clean flash, another rom, the stock rom zip, same results, rom loading, restart and then mi logo and power off.
So I went nuclear and miflash it with the original stock rom, everything went fine there but at the final reboot to system, same thing, rom logo, 2 sec, reboot, mi logo and off.
Can't get adb running now because no usb debug can be enabled as I cant get the system at least running badly to turn it on.,
So I cant reflash anything and twrp is gone because of miflash flashing.
When I let itl connected with a charger, instead of turning off in the second restart, it stays at the charge animation as when you deplete the battery (it charges normaly btw)
Anyone can shine some ideias please? I'm not new to moddind but this is my first xiaomi and I'm stuck

Hey!
You will have to flash through edl mode if fastboot mode is not working

[SYSTEM] Bootloop Xiaomi Redmi 7 (Onclite)

Hello I have a Xiaomi Redmi 7 (Onclite version) - 3GB 32gb, I have had this cell phone for a few months without any problem, I have been able to perform tasks such as unlocking bootloader installing custom roms, among many others, 2 weeks ago I installed the global version 11.7 in recovery mode and the phone worked normal until today, out of nowhere the phone was restarted and the only thing it shows is over and over the Redmi by Xiaomi logo, it is constantly rebooting showing this logo.
Things that I tried to fix this problem:
1. First I thought that was a problem with the room, so I proceeded to go to recovery mode but the phone shows the recovery image and after 4 seconds it reboots.
2. In fastboot mode the phone automatically reboots after 15 seconds approximately, for this reason I can't try with another room, flashing the stock room, only i can change the recovery image but i tried with 3 different versions and doesnt works.
Briefing the phone are constantly rebooting even in recovery mode and fastboot mode
If anyone knows how to solve this problem, I would appreciate it infinitely, thanks

Bootloop Xiaomi Redmi 5 Plus (Vince) Locked Bootloader

I have Xiaomi Redmi 5 Plus with Pixel Experience ROM Android 9, but lately my device suddenly shut down even though the battery still 78%, i tried unplug the battery socket, but still suddenly shut down. So, i wanna flash new ROM which Android Version is 10. But i failed, some people said i must update the firmware, so i update the firmware, but i still failed my device doesn't wanna go to home screen always stuck at Mi Logo, then repeatedly restarted. Then, i tried using Mi Flash Tool and flashing MIUI 9.3 Chinnese Stable ROM. It's Successfully, but i still wanna go to Android 10, then i tried to flash custom recovery and flashing Android 10 ROM, but it's still failed, then i back flashing MIUI 9.5 Global Stable and accidentaly click Clean All & Lock, but after the flash success, errors happened in the home screen, said "Corrupted, Yours Device Is Unsafe Now", then my device repeatedly restarted in the Mi Logo (sometimes it's can go to battery percentage screen), i can go to fastboot and Mi Recovery, but i can't do anything, my bootloader is locked now, tried unlocking the oem in the fastboot but it's failed, tried again flashing in the mi flash tool still failed said "Error Modem", tried flashing with Mi PC Suited 3.0 Chinnese Version the Mi PC Suited flash success but my device still can't go to homescreen and back to mi logo restarting every time. I tried testpoint but my PC can't detect my handphone (it's detect quickly and notification in windows appear "USB Not Recognized", i think the problm is my device always restart every time so i can't detect my device in my pc. So, anyone can help me to fix this problm (device restart every time in Mi Logo with locked bootloader). i am very grateful if anyone can help me.

crackmymind403 said:
I have Xiaomi Redmi 5 Plus with Pixel Experience ROM Android 9, but lately my device suddenly shut down even though the battery still 78%, i tried unplug the battery socket, but still suddenly shut down. So, i wanna flash new ROM which Android Version is 10. But i failed, some people said i must update the firmware, so i update the firmware, but i still failed my device doesn't wanna go to home screen always stuck at Mi Logo, then repeatedly restarted. Then, i tried using Mi Flash Tool and flashing MIUI 9.3 Chinnese Stable ROM. It's Successfully, but i still wanna go to Android 10, then i tried to flash custom recovery and flashing Android 10 ROM, but it's still failed, then i back flashing MIUI 9.5 Global Stable and accidentaly click Clean All & Lock, but after the flash success, errors happened in the home screen, said "Corrupted, Yours Device Is Unsafe Now", then my device repeatedly restarted in the Mi Logo (sometimes it's can go to battery percentage screen), i can go to fastboot and Mi Recovery, but i can't do anything, my bootloader is locked now, tried unlocking the oem in the fastboot but it's failed, tried again flashing in the mi flash tool still failed said "Error Modem", tried flashing with Mi PC Suited 3.0 Chinnese Version the Mi PC Suited flash success but my device still can't go to homescreen and back to mi logo restarting every time. I tried testpoint but my PC can't detect my handphone (it's detect quickly and notification in windows appear "USB Not Recognized", i think the problm is my device always restart every time so i can't detect my device in my pc. So, anyone can help me to fix this problm (device restart every time in Mi Logo with locked bootloader). i am very grateful if anyone can help me.
Click to expand...
Click to collapse
finally how u solved this bro

amrittech said:
finally how u solved this bro
Click to expand...
Click to collapse
Hello, sorry for late reply. The real problem is my battery, my battery leaked and was not correct, I finally bought a new battery in the online shop (this is the reason why my device is always restart). And about the locked bootloader, the only way is with test point mode, I opened the back case and plugged in a certain point using tweezers (you can try another tool), for more details you can look for the tutorial on youtube or google. Good luck

Flashed wrong recovery. Re-flashed correct recovery. Installed ROM. Phone turns off randomly while plugged out of charger and says no battery left.

Please help me out as I messed my phone up real bad recently and I need to fix it as soon as I can as I have interviews right now and need to be updated with them.
So here's what I did:
I was using Pixel Experience ROM on Android 12, with OrangeFox recovery, it was working fine with no major issues.
I really wanted to try out Android 13 though it's still in Beta but I have heard good things about it, specially the one by Project Elixir.
But since I was already using Pixel Experience and loved the ROM so much, I decided to be on the safer side and look if they have a Android 13 ROM for my phone.
That's where the story began, I mistook the Redmi Note 7 forum (lavender) as Redmi Note 7 Pro forum, I forgot how they were two separate devices.
So I flashed the Redmi Note 7 recovery on my phone and it it didn't boot into recovery when I tried it to, then I downloaded the original (correct one) from OrangeFox's official site and flashed it after which the recovery works. But then as I tried installing the new ROM, my adb sideload kept getting stuck at "Starting ADB Sideload feature" and I couldn't make it work, so I flashed the new OS from my sdcard. It was all fine, I set it up and was loving the experience until I plugged it out of the charger. After a few minutes of plugging it out of the charger, it literally started rebooting and it restarts just in the middle of the boot animation. And when I manually power it on by pressing and holding the power button, it displays that It has no charge left.
I tried flashing quite a few other ROMs too, even Android 12 and 13 both, and at a point for some reason it also showed "system has been destroyed. press the power button to shut down" while booting into recovery but it went away once I re-flashed the recovery, and after no luck, I flashed MIUI but the same thing still persists.
I read in a few forums that it might be a battery issue which I too thought at first but the fact that it happened exactly after I flashed the wrong recovery bothers me. I thought installing the stock MIUI rom through fastboot would solve it by replacing every corrupted files and partitions but the issue seems to persist.
What might have been the issue and what can I do to fix it, and can flashing a wrong recovery cause this even if I have flashed the right one just after that?