Related
Searched but not found a similar problem that has a solution. I ran my battery dead by mistake and now all it does is restart after a few seconds on semaphore logo if unplugged, or keep looping buffering circle/battery charge symbol when plugged in. 3BC takes it to download mode but it again restarts after a few seconds...no way near enough to flash anything. Any Ideas?
I was running latest makay rom (2.8.0) and Semaphore 2,9,15s......this seems pretty fatal to me but if someone knows better ill be a very happy man.
Thanks.
Keep it plugged in for a few hours and see if this fixes it.
I have quite the same issue with my SGS i9000. Im running on slim bean 4.1.2 i think and semaphore (quessing the same as above)
So the battery got drained to zero. I charged the battery to full capacity while my phone was turned off. It did this okay and charged battery to 100%. Then i booted my phone only to find out it to start looping in boot. (Start screen to semaphore and then restarts.)
i removed the battery for about an hour, and rebooted the phone but it didn't help at all.
Can't get into recovery (vol up + home + power), though it did go into download mode.
snapper.fishes Keep it plugged in for a few hours and see if this fixes it.
Click to expand...
Click to collapse
As i plugged my phone in in to charger it shows as the battery would be empty,but it doesn't begin to charge it.
Ill be happy to answer if i forgot to mention something important according this matter.
If you can go into download mode but not recovery mode, there is only one thing that you can do - flash an odin rom.
Sent from my Nexus 4 using Tapatalk 2
snapper.fishes said:
If you can go into download mode but not recovery mode, there is only one thing that you can do - flash an odin rom.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
ill try that.
Thanks for the quick answer. Now lets see if that helps..
Tried keeping it plugged in for a few hours but with no joy, odin still recognises the device for the tiny bit of time that the phone it stays on, seen a few comments suggesting it's a battery problem. Have ordered a new one and will see what happens then. The old one was made in Sept 2010 and rarely been turned off since,so i guess its probably to be expected. Will post back when i get the new battery for other peoples future reference.
jwpil said:
Tried keeping it plugged in for a few hours but with no joy, odin still recognises the device for the tiny bit of time that the phone it stays on, seen a few comments suggesting it's a battery problem. Have ordered a new one and will see what happens then. The old one was made in Sept 2010 and rarely been turned off since,so i guess its probably to be expected. Will post back when i get the new battery for other peoples future reference.
Click to expand...
Click to collapse
Hello
I have a Samsung Galaxy S exactly with this problem.
It has cyanogen mod installed.
When i try to turn it on, it shows the default Samsung logo, and then the cyanogen mod screen, it blinks, and displays the cyanogen mod again. After that it reboots and returns do displaying the Samsung logo. ... Inifinite loop!
When i try to plug it in to charge, it shows the battery logo, and a "waiting" or "starting" to charge, blinks, reboots, starts recharging, another loop.
Both loops only stops by removing the battery.
Exactly as this thread describes.
Also, i cannot enter recovery mode: volume up + home + power, but it can enter download mode: volume down + home + power.
Is there any way of getting it to boot other than deleting everything on the phone, as i assume reflashing it would do?
banid0 said:
Hello
I have a Samsung Galaxy S exactly with this problem.
It has cyanogen mod installed.
When i try to turn it on, it shows the default Samsung logo, and then the cyanogen mod screen, it blinks, and displays the cyanogen mod again. After that it reboots and returns do displaying the Samsung logo. ... Inifinite loop!
When i try to plug it in to charge, it shows the battery logo, and a "waiting" or "starting" to charge, blinks, reboots, starts recharging, another loop.
Both loops only stops by removing the battery.
Exactly as this thread describes.
Also, i cannot enter recovery mode: volume up + home + power, but it can enter download mode: volume down + home + power.
Is there any way of getting it to boot other than deleting everything on the phone, as i assume reflashing it would do?
Click to expand...
Click to collapse
I also can't enter recovery, doesn't have time to boot that far. If it is like mine then you will be unable to stay in download mode for long enough to flash anything...if you can get to download and it not reboot again, you have some hope. You could possibly flash a different kernel via odin, semaphore possibly, and see if that helps, but if not you would have to flash back to stock and re-root etc (data will be lost). I will report back when i get a new battery and see if that is the issue (Friday Hopefully), I feel it might be battery issue because my ROM had been running perfectly for days and it started when i let battery completely discharge.
banid0 said:
Hello
I have a Samsung Galaxy S exactly with this problem.
It has cyanogen mod installed.
When i try to turn it on, it shows the default Samsung logo, and then the cyanogen mod screen, it blinks, and displays the cyanogen mod again. After that it reboots and returns do displaying the Samsung logo. ... Inifinite loop!
When i try to plug it in to charge, it shows the battery logo, and a "waiting" or "starting" to charge, blinks, reboots, starts recharging, another loop.
Both loops only stops by removing the battery.
Exactly as this thread describes.
Also, i cannot enter recovery mode: volume up + home + power, but it can enter download mode: volume down + home + power.
Is there any way of getting it to boot other than deleting everything on the phone, as i assume reflashing it would do?
Click to expand...
Click to collapse
Flashing will only delete app data. All your photos and music files will remain.
Just an update... Battery hasn't arrived yet due to snow here. But just by chance I left the phone bootlooping without charger in and it randomly decided to not bootloop. Was able to flash stock with odin root, upgrade to CM 10.1 and restore my nandroid. Oh well.
Sent from my GT-I9000 using xda premium
jwpil said:
Searched but not found a similar problem that has a solution. I ran my battery dead by mistake and now all it does is restart after a few seconds on semaphore logo if unplugged, or keep looping buffering circle/battery charge symbol when plugged in. 3BC takes it to download mode but it again restarts after a few seconds...no way near enough to flash anything. Any Ideas?
I was running latest makay rom (2.8.0) and Semaphore 2,9,15s......this seems pretty fatal to me but if someone knows better ill be a very happy man.
Thanks.
Click to expand...
Click to collapse
[SOLVED]
I recovered my Galaxy Y(s5360) by flashing another kernel from recovery mode in those few seconds for which recovery mode was starting...
I tried that but got soft brick, not enough time to flash kernel image. My power button is now broken so I feel that it may have been stuck in the on position. Think it's stuck in off now. Oh well
Sent from my GT-I9000 using xda premium
Hi I have the same problem on my Asus tf101 the battery ran out during upgrade and now it is looping on Asus title screen pls help me
Hello, I'll start with writing all the things i did:
I flashed JenaMIUI v1.29 succesfully then i waited about 30 minutes at the boot image, then I got the battery out, tried again another 10 minutes stuck at the boot image. After that I reflashed JenaMIUI v1.29 wiped data etc...same thing, stuck at boot image, I got the battery out and back in, one time just after turning on the phone ( before the boot image appear). Then I could'nt start the phone in recovery or normal or download mode. After some tries and leaving the phone for a few minutes i managed to start it normally( but still stuck at boot image) , so I wasn't able to get to recovery, one time I managed to power it up with the charger on, it showed a circle 1/4 full and then went to boot image. Now I'm not able to power up the phone at all, I tried getting the battery out and back in several times. When I connect the charger to the phone with no battery in it, it shows a black screen for a second then nothing. I am not able to start it in recovery or any other way. Is this a battery problem or sth like the mother board ? The bin counter is set to 0 (using triange away), can I take it to service ?
One more thing, when i managed to start it normally and was stuck at boot image i pressed all keys(vol up,down,home,power) and went into a black screen saying something with ARM ..idk.
Is this a battery problem or a brick ? What can I do ?
EDIT: I think the problem was caused by pulling out the battery right after powering on the phone, solution...disconnect battery from phone leave it for 10 minutes, hold power button for 30seconds then turn on the phone in download mode and flash stock...that worked for me
Are you stuck on Miui bootanimation?
Now i can't get it to turn on...i tried replacing the battery , but when i press power nothing happens
Edit: I'm pretty sure is battery problems because I pulled out and put in the battery very fast ...
no, never pull out battery while the device is on splash screen. Wait till boot animation at least. In that moment the kernel is being loaded. This is also causing the recovery bug. People get boot-loop and reset their phone by pulling out the battery. It's actually true, it's the same as if you turn off your PC by unplugging it from power cord.
So if the kernel has some problems because i pulled the battery out while it was loading...can I take it to service ? Can they see what ROM I have installed regardless of my 0 bin counter ? Will they give me a new phone or sth ? Will a lie like...I tried to change the grey case with the orange case and the battery fell out while I reseted the phone work ?
EDIT: I managed to "repair" my phone ! I used a method I found on the internet. I hold the power button for 30 seconds ( while the battery was disconnected) and then put the battery in and I managed to get it in download mode and flash stock rom, now everything works great)
Sorry for the inconvenience, i wrongly packed the rom
RageFoxtrot said:
Sorry for the inconvenience, i wrongly packed the rom
Click to expand...
Click to collapse
No problem...i knew the risks I was taking...and as long as everything turned out fine, It's all good.
Hey guys, I've got a bit of a problem after the latest 4.3 update. My phone battery went to 7% and then suddenly to 0%, upon which it turned off. Now whenever I try to turn it on the red light flashes and whenever I try to turn it on whilst charging (because I don't think it charges if I just leave it plugged in), it just enters a reboot cycle, whereby it goes to the lock screen, shows the "Shutting Down" window and reboots. I have no clue how to fix this.
I don't really care about the phone at this point, but I do have some photos I want to keep from there...
Any ideas? The software hasn't been pampered with.
same here
hey, feeling with you.
I recently updated my Xperia T to 4.3.
While in 4.1.2 the "low battery" behavior was quite weird, as my T did not charge (no red LED), I was able to get it back to life by pressing and holding the power button for quite some time, lets say 5 min. or so, as it was loading then. This was independent from whether it was exhausted (blinking red LED) or "simply of"(not blinking but not charging anyways).
Through this whole power pressing procedure (I just wrapped the cord around the phone several times) the LED was red and the phone was charging, but it did not turn on. After the 5 min. I freed the T an hit the power button again. Now it was booting as expected and did not immediately go off again.
On 4.3 unfortunately this does not work anymore . The phone just tries to boot and enters the reboot cycle as you described (with the difference that it does shut down instead of reboot).
Now first I would like to know, if your T behaved like mine under 4.1.2 (guessing that was your last Version too). From what I've read I assume that wasn't really normal behavior. I think there must be something wrong with the hw, as my 4.1.2 was neither unlocked nor modified in any other way.
Second I would advise you boot into recovery and select boot into bootloader* (if you have installed one) or connect your T to your PC and boot into flashmode (power+vol.down I guess) as it might charges in there. The recovery worked for me, flashmode should work, but I never tried.
Finally I guess chances are good, that your device works totally normal if it gets charged again (just don't let it run out of energy again )
btw. does the Xperia T normally charge while it's powered off? Anyone has send his phone back on warranty because of charging problems?
good luck to you,
wk
*I am using this 4.3 rom (http://forum.xda-developers.com/showthread.php?t=2647459) atm, as I have root there. But the recovery is really buggy right now so it just restarts all the time. I'm not quite sure where the "boot into bootloader" option gets you ( never heard, that you could boot into bootloader on an xperia device) but the LED shines blue and the T charges and that's important right?
Yeah, my T would sometimes do that when the battery completely drained. I'd have to hold the button for a few minutes while the red light was on until it booted and started charging autonomously.
Now that doesn't work. It doesn't charge when it's off and when I connect it to the charger and turn it on, it restarts. Eventually though the battery drains completely and the old trick works again, but even when it manages to boot to the lock screen, it shows 0% battery again and restarts.
I've tried turning it on while holding the power+down button and charging. The green light came on and disappeared but it started rebooting again. Same with connecting it to my PC.
Can you remove the battery?
Same thing happens to mine,and i just remove battery,plug it without battery,it starts,then put the battery back on.
And it charges fine.
Sent from my Arc S using Tapatalk 2
herokickxx said:
Can you remove the battery?
Same thing happens to mine,and i just remove battery,plug it without battery,it starts,then put the battery back on.
And it charges fine.
Sent from my Arc S using Tapatalk 2
Click to expand...
Click to collapse
But the battery is inbuilt, no? Would I have to disassemble it?
KalST said:
But the battery is inbuilt, no? Would I have to disassemble it?
Click to expand...
Click to collapse
So I think you are facing the same issue as mine... the phone has no time to charge. So what I did was flash an OmniRom with only the SystemUI apk and launcher apk. The intention was to make the boot time shorter so that the battery will not go down by the time it boots. But it ended up causing a bootloop: it was constantly stuck in the bootanimation. And it does charge during the bootanimation. So I let it be like that for about 30 minutes, rebooted to recovery and flashed the stock rom. And all my data was safe. This is more like a fluke so try it and maybe it would work.
If you can disassemble it, then yes, you can do the battery thing. There is just one screw under the SIM flap. I didn't do it because my screw driver kit was borrowed.
The battery trick worked! Now it discharges really fast though.
5% in less than 5 minutes...
KalST said:
The battery trick worked! Now it discharges really fast though.
5% in less than 5 minutes...
Click to expand...
Click to collapse
Try recalibrating
Sent from my Arc S using Tapatalk 2
herokickxx said:
Try recalibrating
Sent from my Arc S using Tapatalk 2
Click to expand...
Click to collapse
How do u recalibrate the battery?
Hi!,
Today I was using my Moto g 2014 LTE XT1072 and suddenly it crashed and it got stuck in a bootloop. Im running cyanpop 6.0.1 and TWRP as recovery. Now I get the unlocked bootloader warning, the fibration and than it goes black. Sometimes it get to see a small portion of the cyanpop boot animation, but it stil goes black after that. I can't get into recovery. If I hold the power and volume down button the bootloop stops for 20 secs. After that it begins again. My PC does not spot the phone when I plug it in with Motorola Device Manager installed.
I really do not know what to do anymore. Do I have to buy a new phone? Please save me from the suffering. If you need any more information please ask.
EDIT: Good news everyone! After the battery drained and leaving it alone for 24 houres the phone booted normally. Thanks guys for the help!
have you tried to enter in fastboot mode?
Zagomah said:
have you tried to enter in fastboot mode?
Click to expand...
Click to collapse
Well I can't get into it from recovery, because I can't get excase it. My Pc did start seeing it when its in 'charge mode' (not sure what the real name is), but when I type 'adb devices' in minimal ADB and Fastboot it just says 'list of devices attached'. And when I try 'fastboot devices' it does nothing. Not sure what to know.
Captain_Bacon said:
If I hold the power and volume down button the bootloop stops for 20 secs.
Click to expand...
Click to collapse
While powered off and no cables connected
hold power + vol-down 3/4 seconds (screen stay black) then release the power and keep vol-down pushed (bootloader screen is visible now) release vol-down, .
Not working ? are you sure ?
dr.nic said:
While powered off and no cables connected
hold power + vol-down 3/4 seconds (screen stay black) then release the power and keep vol-down pushed (bootloader screen is visible now) release vol-down, .
Not working ? are you sure ?
Click to expand...
Click to collapse
Will try this at home!
Nope, still the same thing. The loop stops for 20 secs and just continues after
Captain_Bacon said:
Hi!,
Today I was using my Moto g 2014 LTE XT1072 and suddenly it crashed and it got stuck in a bootloop. Im running cyanpop 6.0.1 and TWRP as recovery. Now I get the unlocked bootloader warning, the fibration and than it goes black. Sometimes it get to see a small portion of the cyanpop boot animation, but it stil goes black after that. I can't get into recovery. If I hold the power and volume down button the bootloop stops for 20 secs. After that it begins again. My PC does not spot the phone when I plug it in with Motorola Device Manager installed.
I really do not know what to do anymore. Do I have to buy a new phone? Please save me from the suffering. If you need any more information please ask.
EDIT: Good news everyone! After the battery drained and leaving it alone for 24 houres the phone booted normally. Thanks guys for the help!
Click to expand...
Click to collapse
Nice to know. Moto G family phones tend to suffer from battery-motherboard problems, usually related to current issues. Is your charger at least 1.0A? My Thea's battery drained at school, I tried to connect it to a generic charger and the phone misbehaved and became trapped in a 0% screen loop, and did not appear to grab some charge. I thought to myself "Oh no! My expensive phone is now ruined forever and my warranty is void! What I'm gonna do?" But I walked home, connected it to my old reliable Samsung charger to see what happens and voila! The phone started charging and I could turn it on again.
benjausen said:
Nice to know. Moto G family phones tend to suffer from battery-motherboard problems, usually related to current issues. Is your charger at least 1.0A? My Thea's battery drained at school, I tried to connect it to a generic charger and the phone misbehaved and became trapped in a 0% screen loop, and did not appear to grab some charge. I thought to myself "Oh no! My expensive phone is now ruined forever and my warranty is void! What I'm gonna do?" But I walked home, connected it to my old reliable Samsung charger to see what happens and voila! The phone started charging and I could turn it on again.
Click to expand...
Click to collapse
I used my Nvidia Shield Tablet charger, which is pretty beafy. I experienced somewhat the same thing. Did yours keep trying to boot aswhile?
Captain_Bacon said:
I used my Nvidia Shield Tablet charger, which is pretty beafy. I experienced somewhat the same thing. Did yours keep trying to boot aswhile?
Click to expand...
Click to collapse
Kind of. The phone would not respond nor turn it's LED on. When connected into any charger the phone screen would turn on in the 0% battery screen. If I touched anything, the phone turned off and the 0% screen appeared again. Also sometimes it would just appear again like crazy, like if I killed the bootloader or something alike. After connecting to the Samsung charger, the 0% screen appeared again and the screen turned off. I didn't touch anything out of fear. After three minutes, the Bootloader Unlocked message appeared and finally the phone booted to TWRP's charging screen. I let it charge to 4% and tried to start the phone. The phone booted into CM12.1 and problem solved. I hope these issues never happen to us again. It would mean motherboard degeneration/wearing out/side effect from bootloader unlock and flashing or something alike. Thanks for the answer.
benjausen said:
Kind of. The phone would not respond nor turn it's LED on. When connected into any charger the phone screen would turn on in the 0% battery screen. If I touched anything, the phone turned off and the 0% screen appeared again. Also sometimes it would just appear again like crazy, like if I killed the bootloader or something alike. After connecting to the Samsung charger, the 0% screen appeared again and the screen turned off. I didn't touch anything out of fear. After three minutes, the Bootloader Unlocked message appeared and finally the phone booted to TWRP's charging screen. I let it charge to 4% and tried to start the phone. The phone booted into CM12.1 and problem solved. I hope these issues never happen to us again. It would mean motherboard degeneration/wearing out/side effect from bootloader unlock and flashing or something alike. Thanks for the answer.
Click to expand...
Click to collapse
No probs my friend and I wish you the same. Let the moto gods protect us.
Hello,
My costumer tried to update his Redmi Note 11 from 13.0.9 to 13.0.12 rom via Update App, I don't know if he made something wrong, but now the phone won't charge and not turning on.
When I put the charging cable, the battery symbol blink some times but nothing happens. I'm sending a video that shows it.
I can't get into fastboot mode and when I plug it on PC nothing happens, only the battery symbol blinks and Windows not recognize the phone
Can this phone be saved?
Thank for all help in advance.
rover_ said:
Hello,
My costumer tried to update his Redmi Note 11 from 13.0.9 to 13.0.12 rom via Update App, I don't know if he made something wrong, but now the phone won't charge and not turning on.
When I put the charging cable, the battery symbol blink some times but nothing happens. I'm sending a video that shows it.
I can't get into fastboot mode and when I plug it on PC nothing happens, only the battery symbol blinks and Windows not recognize the phone
Can this phone be saved?
Thank for all help in advance.
Click to expand...
Click to collapse
My guess is that they tried to update when the battery was so discharged, then the update didn't finish correctly, still seems no battery.
When you charge the battery again, try to enter to recovery mode and do a factory reset, try to boot.
To enter to fastboot mode you can, either press volume down + PWR button, or pressing volume down and at same time, connect to your PC, but not much you can do through it, if the bootloader is locked, and plus, the user didn´t start the process to unlock it.
SubwayChamp said:
My guess is that they tried to update when the battery was so discharged, then the update didn't finish correctly, still seems no battery.
When you charge the battery again, try to enter to recovery mode and do a factory reset, try to boot.
To enter to fastboot mode you can, either press volume down + PWR button, or pressing volume down and at same time, connect to your PC, but not much you can do through it, if the bootloader is locked, and plus, the user didn´t start the process to unlock it.
Click to expand...
Click to collapse
SubwayChamp said:
My guess is that they tried to update when the battery was so discharged, then the update didn't finish correctly, still seems no battery.
When you charge the battery again, try to enter to recovery mode and do a factory reset, try to boot.
To enter to fastboot mode you can, either press volume down + PWR button, or pressing volume down and at same time, connect to your PC, but not much you can do through it, if the bootloader is locked, and plus, the user didn´t start the process to unlock it.
Click to expand...
Click to collapse
Thanks for your answer.
I charged the phone for 24 hours and it is the same as it appears in the video. It didn't charge and it won't turn on. Only the battery symbol appears.
I can't get into recovery mode or fastboot mode.
I tried to connect it to the PC holding Volume- but nothing happens, the same battery symbol appears
Bootloader is locked.
rover_ said:
Thanks for your answer.
I charged the phone for 24 hours and it is the same as it appears in the video. It didn't charge and it won't turn on. Only the battery symbol appears.
I can't get into recovery mode or fastboot mode.
I tried to connect it to the PC holding Volume- but nothing happens, the same battery symbol appears
Bootloader is locked.
Click to expand...
Click to collapse
Well, you don't need to charge for 24 hours, it seems to me that something in the hardware is damaged or was disconnected, like the charging flex connector, it could be an internal error, you should check it with the help of a technician, the symbol shows no charge at all. After you solve it, at hardware level, then you should try some tips at software level.
SubwayChamp said:
Well, you don't need to charge for 24 hours, it seems to me that something in the hardware is damaged or was disconnected, like the charging flex connector, it could be an internal error, you should check it with the help of a technician, the symbol shows no charge at all. After you solve it, at hardware level, then you should try some tips at software level.
Click to expand...
Click to collapse
RIGHT
Hi. I am facing the same issue exactly. However, i didnt update or anything. My phone was discharged after day of use. So i tried to recharge it normally and its not getting charged or turning on. Did you resolve the issue? any tips
rover_ said:
Hello,
My costumer tried to update his Redmi Note 11 from 13.0.9 to 13.0.12 rom via Update App, I don't know if he made something wrong, but now the phone won't charge and not turning on.
When I put the charging cable, the battery symbol blink some times but nothing happens. I'm sending a video that shows it.
I can't get into fastboot mode and when I plug it on PC nothing happens, only the battery symbol blinks and Windows not recognize the phone
Can this phone be saved?
Thank for all help in advance.
Click to expand...
Click to collapse
Hello brother. Im facing the s
rover_ said:
Hello,
My costumer tried to update his Redmi Note 11 from 13.0.9 to 13.0.12 rom via Update App, I don't know if he made something wrong, but now the phone won't charge and not turning on.
When I put the charging cable, the battery symbol blink some times but nothing happens. I'm sending a video that shows it.
I can't get into fastboot mode and when I plug it on PC nothing happens, only the battery symbol blinks and Windows not recognize the phone
Can this phone be saved?
Thank for all help in advance.
Click to expand...
Click to collapse
Hello brother. Im facing the same exact issue. did you fix the phone. Any way to fix it?
Today my phone has fully discharged and I have the exact same issue.
Impossible to boot and I cannot charge it, as it results as the blinking of the battery icon...
On my side, if I plug the USB-C, it does not even says it charges / but it vibrates each ~5sec with the same (empty) battery icon...
doc4dev said:
Today my phone has fully discharged and I have the exact same issue.
Impossible to boot and I cannot charge it, as it results as the blinking of the battery icon...
On my side, if I plug the USB-C, it does not even says it charges / but it vibrates each ~5sec with the same (empty) battery icon...
Click to expand...
Click to collapse
hi..i have already posted this on a thread in the morning. i have same exact issue.
I dropped the email to xiaomi and they after lot of back and forth emails, and trying everything out, they asked me to visit a service center. apparently after doing some research the only way to fix it is by opening the phone and disconnecting the battery and connecting it again.
My phone was less than a month old and ordered from amazon. they are going to accept the return request luckily.
I know guys, no one likes to disassemble a device or take it to a repair service center, but the issue is clearly related to a hardware fault, i.e. battery, charge flex connector or whatever they are called.
Majid6165 said:
hi..i have already posted this on a thread in the morning. i have same exact issue.
I dropped the email to xiaomi and they after lot of back and forth emails, and trying everything out, they asked me to visit a service center. apparently after doing some research the only way to fix it is by opening the phone and disconnecting the battery and connecting it again.
My phone was less than a month old and ordered from amazon. they are going to accept the return request luckily.
Click to expand...
Click to collapse
I had the same issue, wouldn't boot or display anything, so I took the phone (spesn) to a service center.
The technician told me all he did to repair the phone was a software upgrade... No problems since then, it probably can be done at home somehow...
v|r|s said:
I had the same issue, wouldn't boot or display anything, so I took the phone (spesn) to a service center.
The technician told me all he did to repair the phone was a software upgrade... No problems since then, it probably can be done at home somehow...
Click to expand...
Click to collapse
hello guys, i have the same issue facing right now, it's been 7 hrs charging. This is the first time that I drained the battery. Have you all tried to fix it into a technician? because I'm still worrying, and I already tried the other solutions.
I wanna fix my phone as soon as possible
vanellopevonn said:
I wanna fix my phone as soon as possible
Click to expand...
Click to collapse
It seems a hardware issue, but...
Some bad flashing cycle can cause the display not "turning on" at all, but really, it's just not showing a thing, to cover and check this possibility, you should flash a different firmware, just check out, the state your device gets connected, and try flashing a firmware.
For everyone who has this problem, remember that with locked bootloader it is impossible to flash the official rom by miflash.
The only alternative you have at the moment is to try to start the phone in EDL mode and that means opening the phone and seeing how to do the test point.
IF the pc recognizes it, they are in luck and it can be recovered, but due to xiaomi policies, only some people have accounts authorized to flash by EDL and charge for the service, many do it remotely and are found on telegram.
All the lot of issues, users are reporting on this device, they are realizing that Xiaomi is forcing them all to unlock the bootloader.
Unlocking the bootloader may be the fastest and cheapest way to escape from an eventual disastrous scenario.
I have the same issue with my Redmi Note 11, I successfully update it, I have 3 other chargers and cables I try all possible methods to eliminate possibilities even check type-c port but phone not charging after mini 13.0.12 update. How we gonna have fix this or is the are a plan from xiaomi to have solution?