Related
Hello everyone, long time reader, first time poster (with a real query).
Actually last Friday my cappy started to show 100% of the battery after being for some time in use, so I reboot it trying to solve the issue.
After the boot, the cell shows the Initially Battery screen for 2 seconds with the battery without charge then turns off. Tried several times and also using a second battery with full charge and same problem persisted.
10 minutes later without having a battery inside the phone, it boots but when I rebooted the problem arises again.
This weekend I installed Illuminance 3.01, after that I have installed CM9 (very nice ROM) and the battery problem still is happening. I am able to use the phone but I don´t know for how much more.
Any suggestion?
Thanks,
Martin
have you tried to wipe battery stats in recovery ?
Felixcm88 said:
have you tried to wipe battery stats in recovery ?
Click to expand...
Click to collapse
Yesterday night I did a wipe battery stats and the problem still is there.
It starts with the loop and the only way I can start the phone is plugging it then it shows the actual charge of the battery and after that I can boot.
It must be something "deeper" than the rom...
Anybody?
Thanks
Somebody can help?
I am having the exact same issue, stock froyo 2.2 rooted 5 months ago. I'm trying everything before updating to 2.3, I'll let you know if I find a fix, please do the same.
Searching google is not working this time, it's been 3 days...
Things I've tried:
1- From recovery, boot phone. Problem persists after phone is turned off.
2- Boot from revovery, then reset to factory settings, after rese, same issue.
3- Wipe cache from recovery. Problem still there.
4- Wipe cache+user data from recovery. Same thing.
5- repeating 1-4 without SD card or SIM card.
- Wipe battery data... nothing...
- Unrooting, same issue, rooted again.
- Run root fixes with Titanium backup. Same...
- Removing battery for hours, while charging it externally, replace battery, same issue.
All to no success. Things yet to try:
- Update to 2.3 using kies
- Update to beta 2.3.5 using odin
- Update to custom rom, maybe try 3 or 4 different...
- Cry, then save and buy a new phone, use cappy as shiny paperweight...
Please let me know if you could fix it...
I'm not sure what you mean when you say "initial battery screen."
But if I am to understand the rest, your problem is:
initial boot - runs fine, but battery stays at 100% no matter how long it runs.
reboot - phone now says the battery is suddenly dead, and shuts-off.
further reboots - same
You can't get the phone to fully boot till the battery is left out for a while and the phone is fully de-energized.
You have tried a different battery and it behaves the same.
- - - - - -
Have you tried using a known "good" battery? (a new one or one from someone who's phone works fine)
Also, what happens if you plug in the USB while the phone is off? (after the inital boot, when it is stuck in the "dead battery loop.")
Still dead after installing update and 2 custom roms...
Yes I tried a good battery from another cappy, if I plug in the cable it does the same, instead of normally booting, it displays an empty battery and goes off.
I am able to make it work but only entering the restore mode, so I cannot for example be on a trip and reset the phone for whatever reason...
have you tried using a different kernel?
Sent from my SGH-I897 using XDA App
sorry, but how can I try a different kernel? do i need to change the rom?
Nah, kernels can be flashed independent of ROMs just look through development for topics that have "[Kernel]" as the fist word in their title.
If you have gone and loaded two custom ROMs and it still persist then it's not a kernel issue. As the kernel is always changed along with the ROM.
That said, I can only think of two other possibilities: one being dirt or such making a short in the contacts of the usb (does it sometimes think it is plugged in when it's not), two something in the circuitry for the battery randomly went bad.
Try cleaning the socket for the usb. If that does not fix then assume the worst
leaked from my ICS- FUSED SGS I897 contaminating you via XDA app.
Ok, here's the thing, I left it without the battery for 24 hrs, then it was worst. The phone would not turn on at all. However, after that I tried putting the battery in while holding the power button, it worked!!! it's better than having to connect to the computer, but still, I don't want to have to do this every time... flashing roms now to try again.
We're getting somewhere now...
DaNaRkI could be right about it being a circuitry problem (which would suck). With that in mind, have you checked to make sure the prongs which connect the battery to the phone are still in good shape?
When you flashed the roms, are you doing complete wipes? (wiping the cache/dalvik/data)? It might be worth it to go one step beyond that and format all the partitions and then reflash. I think if you do that, you could basically rule out any software problems.
Be sure to back up your data!
P.S. When you do all this wiping and formating and reflashing, boot up and check to see if the problem is still there before you put your data back on jic there is some weird corruption in your data which is causing this.
ok.
have you checked to make sure the prongs which connect the battery to the phone are still in good shape?
yes I have, they're perfect
When you flashed the roms, are you doing complete wipes?
many times, actually
I have yet to format all partitions, how can I do that?
Thanks!!
and yes, all my data is well backed up in my PC and cloud...
---------- Post added at 12:31 AM ---------- Previous post was at 12:09 AM ----------
this is rather odd, just tried to factory reset again, then restarted using the battery method, then... turned it off, and now it boots normally!!!
Thanks for your help !!!
I have the same problem. What exactly did you do? I use a custom rom, and I flashed stock gingerbread 2.3.4.
Formatting the partitions won't do anything, since the phone won't even turn on sometimes. So when exactly did this problem start happening? Was it after a particular flash or other incident?
My sincerest apologies if this has been discussed elsewhere, but I've searched high and low in Google and XDA without result.
I recently rooted my P3 and then flashed CM10. Took me a few goes (first time 3G wasn't working etc.), but each time I factory reset, wiped cache and dalvik cache before and after flashing. I eventually got it working just fine, except for the battery not displaying properly. It always said it was charging, even when it wasn't, and it wouldn't charge to 100%, instead stopping at 99%. I used the battery calibration mod, and tried to wipe the battery stats via CWM recovery, but to no avail.
Other than that, and the auto rotation flipping to the opposite side you turn (I understand this is a known bug), everything was running smoothly so I decided to do a backup via CWM recovery. Once everything was completed I booted back up. It all was working as it had before, until I tried to power down. The screen went black, but shortly the Samsung Galaxy splash screen came on and it booted up again. I tried wiping the cache and dalvik cache, wiping battery stats, but it still will not stay powered down. The only exception is when I have it plugged in and charging, then it will stay on the battery charging animation instead of rebooting.
Any help would be much appreciated. I really don't want to have to revert to base CWM after tasting the awesomeness of CM10!
Xanthippus said:
My sincerest apologies if this has been discussed elsewhere, but I've searched high and low in Google and XDA without result.
I recently rooted my P3 and then flashed CM10. Took me a few goes (first time 3G wasn't working etc.), but each time I factory reset, wiped cache and dalvik cache before and after flashing. I eventually got it working just fine, except for the battery not displaying properly. It always said it was charging, even when it wasn't, and it wouldn't charge to 100%, instead stopping at 99%. I used the battery calibration mod, and tried to wipe the battery stats via CWM recovery, but to no avail.
Other than that, and the auto rotation flipping to the opposite side you turn (I understand this is a known bug), everything was running smoothly so I decided to do a backup via CWM recovery. Once everything was completed I booted back up. It all was working as it had before, until I tried to power down. The screen went black, but shortly the Samsung Galaxy splash screen came on and it booted up again. I tried wiping the cache and dalvik cache, wiping battery stats, but it still will not stay powered down. The only exception is when I have it plugged in and charging, then it will stay on the battery charging animation instead of rebooting.
Any help would be much appreciated. I really don't want to have to revert to base CWM after tasting the awesomeness of CM10!
Click to expand...
Click to collapse
Which version are you using? It was a known bug in an older ROM, which should have been fixed in the newer ones.
Using the 20120816 version that I got from the link in this thread: http://forum.xda-developers.com/showthread.php?t=1803593
I've also had this problem for awhile, with several different ROM's.
Does fastboot work for you? Cause it doesn't for me, but not sure if related.
Xanthippus said:
My sincerest apologies if this has been discussed elsewhere, but I've searched high and low in Google and XDA without result.
I recently rooted my P3 and then flashed CM10. Took me a few goes (first time 3G wasn't working etc.), but each time I factory reset, wiped cache and dalvik cache before and after flashing. I eventually got it working just fine, except for the battery not displaying properly. It always said it was charging, even when it wasn't, and it wouldn't charge to 100%, instead stopping at 99%. I used the battery calibration mod, and tried to wipe the battery stats via CWM recovery, but to no avail.
Other than that, and the auto rotation flipping to the opposite side you turn (I understand this is a known bug), everything was running smoothly so I decided to do a backup via CWM recovery. Once everything was completed I booted back up. It all was working as it had before, until I tried to power down. The screen went black, but shortly the Samsung Galaxy splash screen came on and it booted up again. I tried wiping the cache and dalvik cache, wiping battery stats, but it still will not stay powered down. The only exception is when I have it plugged in and charging, then it will stay on the battery charging animation instead of rebooting.
Any help would be much appreciated. I really don't want to have to revert to base CWM after tasting the awesomeness of CM10!
Click to expand...
Click to collapse
Are you using the correct recovery? Not sure that you would be able to get as far as you if it were wrong but ...
I caused myself heartache at some point as a result of using the wrong recovery. It gave my weird results too. I am other 16 Aug ROM and I find it pretty damn good.
Here is the right one
http://droidbasement.com/galaxy/roms/cm10/p3/recovery.tar.md5
GaryWS said:
Are you using the correct recovery? Not sure that you would be able to get as far as you if it were wrong but ...
I caused myself heartache at some point as a result of using the wrong recovery. It gave my weird results too. I am other 16 Aug ROM and I find it pretty damn good.
Here is the right one
Click to expand...
Click to collapse
I got the recovery from the same thread I linked above, so pretty sure it was the right one. Just to be sure I downloaded and flashed the one you linked with Odin, but it's made no difference. However, I have (finally) had success in getting the battery to charge to 100%. I kept wiping the battery stats every time I booted up, and powered it down while plugged in and left it on charge when I wasn't using it. After a couple of days (with it on and off charge) it finally said it was fully charged when I powered it on. I have used the battery calibration app with it at 100%, so hopefully it shall begin indicating properly, although it still says it's charging all the time, and the charging animation when it is powered down does not indicate its actual charge level.
As for it not powering down when it's not plugged in... I am still new to rooting and ROMs, but would it be of help if someone who has no problems powering down uploaded their kernel and I flashed that?
Xanthippus said:
As for it not powering down when it's not plugged in... I am still new to rooting and ROMs, but would it be of help if someone who has no problems powering down uploaded their kernel and I flashed that?
Click to expand...
Click to collapse
Re-download the lastest ROM and flash it; the latest ROM does not have that problem.
pruano said:
Re-download the lastest ROM and flash it; the latest ROM does not have that problem.
Click to expand...
Click to collapse
Where would I get that ROM from? The latest one from the link above at the Droid basement is the 16th August version I already have.
Xanthippus said:
Where would I get that ROM from? The latest one from the link above at the Droid basement is the 16th August version I already have.
Click to expand...
Click to collapse
I would recommend you re-download and re-flash it, since others (myself included) have no such problem with that version.
Didn't work. Redownloaded, reflashed, same problem. I even tried to unroot it so that I could flash it all again fresh, but somewhere along the way something has gone wrong. Odin is not working anymore. I can transfer files to and from my tablet, the computer still recognises it when plugged in, and Odin recognises the USB connection too, but if I try to flash something with it, it always says it is unable to open the COM port.
Tried this many different ways, with different roms, nothing seemed to work. Finally, tried AOKP milestone 6 (based on CM9) and it works perfectly. Go figure...
Hi,
I have been running cm10.1 for a while on my galaxy note. I recently upgraded to 10.2 nightlies. Yesterday I opened the stock camera app (not focal) and when i clicked on capture the phone froze. So I had to pull out the battery. After that the phone would not start. I had full charge when my phone froze. When I connect a charger I get a battery logo with a loading circle icon. However this icon keeps flashing like a loop.
I am not able to go into recovery. But I can go into download mode only when I connect a charger or to the computer. However when I press volume up to confirm download mode, it exits it and the battery loop starts again.
Could someone please help me fix the issue.
Thanks
try another battery please
ThaiDai said:
try another battery please
Click to expand...
Click to collapse
Thanks ThaiDai. I put back my old defective original samsung battery and it booted.
I have similar issue. Flashed CM10.2 everything seemed to be working OK until I tried to go back into recovery and flash an update. Will not reboot from an attempt to go into recovery unless you plug in until you get green battery icon, then unplug and phone will boot. Once booted everything seems to work ok, you can reboot phone, download and install from play store, even reboot the phone, but any attempt to go into recovery will cause the device not to restart.
So, I can't flash anything, including a new recovery.. LOL... I'm wondering if this might be a battery issue as well, but I don't have a spare battery to try.
Warning: LONG POST incoming ***
So I think I'm having the worst brick I've ever encountered on this phone, had tons of softbricks before and I could almost always sort them out easily, this one I'm having right now unforetunately is not the same case.
Current situation, phone won't boot up, no logo, no nothing, pressing power on button gives two RED blinks, holding power on gives continuous red led blink, now, vol. Up + power wont work anymore, same as hard reset of vol up+pwr with 3vibrates, it does work a few days ago but not anymore (I'm thinking about the issue of hard reset that results in about 50+ hrs or battery draining and recovery but not so sure if thats the case right now).
I've tried going flashmode but it just wont remain in flashmode, I can enter on flashmode briefly, proceed to flash stock ftf then somewhre along the process, (system.sin i think) phone exits flashmode then red led will show up. Fastboot wont work either.
Last observation i have is during wall charging, initially, when I connect to charger, no led light will show for about 3sec, then GREEN led will show and blink around 5times in about 1min, led disappears for a few sec then straight RED led will show for about 2min, and the cycle goes on and on, been monitoring like this for about 3hrs now, will continue until tomorrow.
Note: worst case, I think battery is flat dead thats why it wont charge, or something got fried during usage, never flashed antything for a few months, last thing I remember is I'm having a series of reboots, during long hours of mobile hotspot. Also worth mentioning, this phone auto reboots when it overheats during charging.
This may be a long shot but if anyone miraculously knows a workaround here other than getting a new one, then that'd be a huge help.
That's all, Thanks!
hi
I'm having a similar problem on my Xperia TL (LT30at). It was running on android 4.1.2 and I tried to flash it with a 4.3 ROM (originally built for LT30p, customized for US). During the process, there was an error while the flashtool was processing system.sin. In my case, there's no LED indication, no vibration, no nothing. The phone just won't respond to any button press combo (the battery was about 80% charged).
Plz help.
RESTORED!
Update: After long hours of battling this bricked mode, I've finally restored my phone! Stock FTF won't go through flashmode no matter what I do but luckily "Fastboot Trick" did the work along with numerous Trial and Errors, basically I was able to access fastboot by following and READING all of the instructions on xperia recovery pages here on XDA, from charging cycles, battery disconnect via opening the phone, flashmode/fastboot access, rubber band trick and so on.
Tried flashing kernel.sin from stock FTF (got into boot logo/bootloops with this), system.sin (can't fastboot flash due to huge file size), and lastly using my current roms (CM12.1 by neo) boot.img and flashing it via flashtool fastboot.this one did the trick allowing me to use my previous kernel along with my still un-wiped ROM data resulting to booting into it's previous working state.
Credits to @gregbradley , @Toledo_JAB and all that contributed to their tools and recovery thread (link below)
ALL IN ONE THREAD[Updated 12/3/13]Read me first!
[GUIDE] Recover 2012 and newer XPERIAs from SOFT-brick
The Key is as long as you're getting a response(if you don't get any, wall charge your phone for 4 ~ 24 hours and see if you can get a red led which then means you can still save your phone), vibrate, led blink, then you can bet you can still recover your phone. You just have to try everything you haven't tried before. That's all!
I had my T also similarly "bricked" last summer. Flashing always resulted in errors. Rubber band while powering helped, but only worked with original Sony charger. No luck with a Samsung one. After several reboots flashing went ok. The phone was stable only with battery almost full. After I replaced the battery, everything works well again. I guess the battery has been damaged by different chargers - a Samsung 2A (for tablet), in-car, and external battery pack. Currently evaluating CM 12.1
LiudasP said:
I had my T also similarly "bricked" last summer. Flashing always resulted in errors. Rubber band while powering helped, but only worked with original Sony charger. No luck with a Samsung one. After several reboots flashing went ok. The phone was stable only with battery almost full. After I replaced the battery, everything works well again. I guess the battery has been damaged by different chargers - a Samsung 2A (for tablet), in-car, and external battery pack. Currently evaluating CM 12.1
Click to expand...
Click to collapse
Good thing replacing battery works for you, though I have recovered my phone, I think mines hotspot module got damaged already due to extensive usage and overheating from before (currently experiencing random reboots right now when data is on), gonna check to see if this is kernel or hardware related.
PS: WhiteNeo's NeoWave(KK) and CM12.1 ROM's(development stopped / best version though is 20151010 afaik) are the fastest I have tested yet. You should check them both .
Xperia TL (LT30at) Hard Bricked!!
Well, it’s pretty much obvious that I have hard bricked my phone.
I’ve been searching over the internet (especially on XDA) about this issue and I’ve realized that I’ve caused my phone’s bootloader to be damaged and that’s why it won’t boot at all. Before unlocking the bootloader, I did not make a TA backup (as I’ve seen in some posts that it is required to restore security units in case of boot failure) and now I don’t know how to fix my phone. Most likely, I need a suitable firmware for my phone to flash it with and hence to restore bootloader, but I haven’t found a firmware for my phone anywhere over the internet.
By the way, my phone is recognized as ZEUS flash device when I connect it to my pc, so I feel like there is a chance to recover it from this brick. I took it to a repair center, they tried JTAG but the guy said it didn’t work. The phone takes the dump but still doesn’t boot.
Could anyone help please?
kain_the_sly said:
Well, it’s pretty much obvious that I have hard bricked my phone.
I’ve been searching over the internet (especially on XDA) about this issue and I’ve realized that I’ve caused my phone’s bootloader to be damaged and that’s why it won’t boot at all. Before unlocking the bootloader, I did not make a TA backup (as I’ve seen in some posts that it is required to restore security units in case of boot failure) and now I don’t know how to fix my phone. Most likely, I need a suitable firmware for my phone to flash it with and hence to restore bootloader, but I haven’t found a firmware for my phone anywhere over the internet.
By the way, my phone is recognized as ZEUS flash device when I connect it to my pc, so I feel like there is a chance to recover it from this brick. I took it to a repair center, they tried JTAG but the guy said it didn’t work. The phone takes the dump but still doesn’t boot.
Could anyone help please?
Click to expand...
Click to collapse
Not that sure when it comes to bootloader errors but I'll try to help, if it's detected on your PC, then you might still be able to recover it (mine is not even detected on my PC the last time it got bricked, but I got it fixed(detected) with proper driver installation: [Drivers] FlashTool Xperia Driver Pack (v1.5) [20140318] by @DooMLoRD), check troubleshooting section if you are using Windows 8 as you might encounter driver signature error during installation .
Question: Does it respond to any action? eg, vibrate, pressing power button just once(if it blinks red LED twice = phone is still alive), soft reset & hard reset, wall charging, fastboot or flashmode when connected to PC?
zakcaree said:
Not that sure when it comes to bootloader errors but I'll try to help, if it's detected on your PC, then you might still be able to recover it (mine is not even detected on my PC the last time it got bricked, but I got it fixed(detected) with proper driver installation: [Drivers] FlashTool Xperia Driver Pack (v1.5) [20140318] by @DooMLoRD), check troubleshooting section if you are using Windows 8 as you might encounter driver signature error during installation .
Question: Does it respond to any action? eg, vibrate, pressing power button just once(if it blinks red LED twice = phone is still alive), soft reset & hard reset, wall charging, fastboot or flashmode when connected to PC?
Click to expand...
Click to collapse
No. It doesn't vibrate, no LED blink, no fastboot or flashmode. The phone is non-responsive to every button press. However, red LED blinks just for once when I connect it to my pc and when the battery is unplugged.
So far, I've a pretty sure idea that the phone is in "dead boot" and somehow I've to restore its security units / TA backup, as the boot partition is corrupted. Unfortunately, I don't have a TA backup. However, I could make use of TA backup from another working LT30at.
P.S. I'm using Windows 7 and there are no driver issues. The phone is recognized by my pc as an ZEUS flash device.
zakcaree said:
Good thing replacing battery works for you, though I have recovered my phone, I think mines hotspot module got damaged already due to extensive usage and overheating from before (currently experiencing random reboots right now when data is on), gonna check to see if this is kernel or hardware related.
PS: WhiteNeo's NeoWave(KK) and CM12.1 ROM's(development stopped / best version though is 20151010 afaik) are the fastest I have tested yet. You should check them both .
Click to expand...
Click to collapse
Hi guys.
I have the same problem i tierd flashing the rom stock..it does't work..flash aborted and phone disconnected avain and again.
But when i remove the battery..phone in wallcharger it shows sony logo and keep restarting..no blinking led no vibration.
Any idea???
Mizouradio said:
Hi guys.
I have the same problem i tierd flashing the rom stock..it does't work..flash aborted and phone disconnected avain and again.
But when i remove the battery..phone in wallcharger it shows sony logo and keep restarting..no blinking led no vibration.
Any idea???
Click to expand...
Click to collapse
Try install stock without battery and then plug it in when u start
alial04 said:
Try install stock without battery and then plug it in when u start
Click to expand...
Click to collapse
Yes i did that...still have the same pb...end of flash session..phone keep disconnecting..and flash aborted!!!
Any advice?
Mizouradio said:
Hi guys.
I have the same problem i tierd flashing the rom stock..it does't work..flash aborted and phone disconnected avain and again.
But when i remove the battery..phone in wallcharger it shows sony logo and keep restarting..no blinking led no vibration.
Any idea???
Click to expand...
Click to collapse
Bootloop usually means boot kernel problem, Can you fastboot? try to fastboot flash your previous ROM kernel and check to see if you can boot normally to your previous rom.
im not using an xperia tl but pretty much thw same issue with my xperia e3 d2212
red light keeps blinking its charging(no logo just saying) tried evry key combination triying to connect to pc says connected for a few secs n then it gets disconnected although i say that its connected im sayin it only based on the sound derz actually no new software or unknown software msgs popping plzzz help me out............ ty in advance
Sunderesh said:
im not using an xperia tl but pretty much thw same issue with my xperia e3 d2212
red light keeps blinking its charging(no logo just saying) tried evry key combination triying to connect to pc says connected for a few secs n then it gets disconnected although i say that its connected im sayin it only based on the sound derz actually no new software or unknown software msgs popping plzzz help me out............ ty in advance
Click to expand...
Click to collapse
You mean red LED blinks during charging? Did you flash anything before this occured? Try first charging it for 2~4hrs, (also check if red LED still flashes during charging after a couple of hours), then try powering it ON... does it boot? If not, try soft reset with your phone (hold vol-up + power button for a few sec), it will vibrate ONCE, that means soft reset, power it ON... does it boot? If not, try hard reset this time (same method as soft-reset, this time hold the buttons longer, you will first get 1 vibrate, just hold it still, then you wil get 3 vibrates = hard reset).. power it ON... does it boot? If not.. try charging it a little longer and repeat the process, see if you can get it to boot that way.
zakcaree said:
You mean red LED blinks during charging? Did you flash anything before this occured? Try first charging it for 2~4hrs, (also check if red LED still flashes during charging after a couple of hours), then try powering it ON... does it boot? If not, try soft reset with your phone (hold vol-up + power button for a few sec), it will vibrate ONCE, that means soft reset, power it ON... does it boot? If not, try hard reset this time (same method as soft-reset, this time hold the buttons longer, you will first get 1 vibrate, just hold it still, then you wil get 3 vibrates = hard reset).. power it ON... does it boot? If not.. try charging it a little longer and repeat the process, see if you can get it to boot that way.
Click to expand...
Click to collapse
I will tell u my problem in detail I have a Sony Xperia e3 d2212 running stock 4.4.2 I rooted it without unlocking bootloader with" kingoroot" later saw a few privacy issues with kingo super user and used "supersume pro" to get super su as superuser and to get rid of kingosuper user
then tried an boot loader unlock with an app named "ez unlock" then tried flashing cwm
the mistake I did was that I flashed the cwm file which was made for my phone running 4.4.4
and now if it is low on battery the red led blinks only when I hold the power button
if I put it on charge for a few hours and then unplug the charger the red led keeps blinking all day long
let me know if u understood
sorry for the confusion though
---------- Post added at 03:05 PM ---------- Previous post was at 03:03 PM ----------
thank you for ur interest bro.......
zakcaree said:
Bootloop usually means boot kernel problem, Can you fastboot? try to fastboot flash your previous ROM kernel and check to see if you can boot normally to your previous rom.
Click to expand...
Click to collapse
thanks but i tried that...without result.cause the phone is not reconized and keep disconnecting
is that a driver problem??
Hello everyone,
I have-or had- MI5 with latest cm14.1 on it, today I downloaded the latest rom from xiaomi.eu -Nougat-. I rebooted into recovery, wiped partitions, flashed the new rom, flashed successfully, and then flashed a font zip, the installer hanged at unmounting system for a long time, I forced rebooting it through holding power button the phone turned off and then never worked. nothing happens, no led when connecting to charger, pc does not recognize the phone at all, no sounds when connecting it. recovery and bootloader does not open. it is completely DEAD. Any help?
same h ere except i didn't get any errors while flashing except the normal command[log] error for all nougat roms. phone is just dead with no signs of life.
iXanza said:
same h ere except i didn't get any errors while flashing except the normal command[log] error for all nougat roms. phone is just dead with no signs of life.
Click to expand...
Click to collapse
I got this error as well,
After some search it seems using a deep flash cable could, I cannot make one currently so maybe you could take a look and try it
http://forum.xda-developers.com/showpost.php?p=69727277&postcount=2
I just checked the second post in the xiaomi eu thread
"- NEVER wipe /system partition manually in your life!"
hmm, I have always done this
Edit:
Many people reporting the same issue their.
There's another way to go to EDL mode which is this
https://www.youtube.com/watch?v=ED96PJ-qYMM
I haven't tried it yet as I don't have copper tweezers.
iXanza said:
There's another way to go to EDL mode which is this
https://www.youtube.com/watch?v=ED96PJ-qYMM
I haven't tried it yet as I don't have copper tweezers.
Click to expand...
Click to collapse
People reported it worked in xiaomi eu thread, gonna try once I have the tools, I wonder why the * dev didn't write "- NEVER wipe /system partition manually in your life!" before the download links
IMTLD said:
People reported it worked in xiaomi eu thread, gonna try once I have the tools, I wonder why the * dev didn't write "- NEVER wipe /system partition manually in your life!" before the download links
Click to expand...
Click to collapse
No clue. I'm taking it to the shop for them to do it for me tomorrow.
https://www.youtube.com/watch?v=ED96PJ-qYMM
Do follow the videos, i was hard brick 2 times but now it's working
The issue is, you flashed the CM14.1 on low battery, this then messed up the battery reading, while your device showed somewhere like 50% infact it was around 10%, what need to be done is, do a hard reset with power button a few times while connected to a charger, use a new charger/cable and let it charge for a long time, itll then switch on and charge, leave it to charge till 100% then do a full wipe including internal storage and install a new OS
Shaky156 said:
The issue is, you flashed the CM14.1 on low battery, this then messed up the battery reading, while your device showed somewhere like 50% infact it was around 10%, what need to be done is, do a hard reset with power button a few times while connected to a charger, use a new charger/cable and let it charge for a long time, itll then switch on and charge, leave it to charge till 100% then do a full wipe including internal storage and install a new OS
Click to expand...
Click to collapse
I don't really think that this is the problem because the "rom" flash completely successfully. I don't think that the font flash would cause all this mess. Anyway, I left it charging overnight and I keep pressing power button with vol +/- but nothing happens. Thanks anyway. it seems I have to either use test points or deep flash cable.
Hard bricked the phone with the same ROM here, tried to solve it with the video's testpoints (making contact between the two dots and plugging the USB).
Fortunately, MiFlash with adb and qualcomm drivers recognized the device. So I flashed many fastboot ROMs (miui 7/8 dev&stable) via MiFlash, but none of them made the device wake up. The only signal of life is the led blinking red when connected to a usb.
Still trying...
EDIT: ok, got it booting now. The red blinking led is actually a good sign, it means low battery. I just let it charge for about 20 min and the led changed to yellow, and then I could boot it up.
It seems like in all that time the phone was plugged into my PC usb port for flashing, it didn't charge the battery. So I think we should take into account what Shaky156 said, just in case.
jiaming2009 said:
Hard bricked the phone with the same ROM here, tried to solve it with the video's testpoints (making contact between the two dots and plugging the USB).
Fortunately, MiFlash with adb and qualcomm drivers recognized the device. So I flashed many fastboot ROMs (miui 7/8 dev&stable) via MiFlash, but none of them made the device wake up. The only signal of life is the led blinking red when connected to a usb.
Still trying...
Click to expand...
Click to collapse
I just revived my mi5 using the test point method, it is rather simple actually.
Make sure you are using miflashtool beta,
I downloaded this rom china developer
I noticed that even though I chose save user data, I still lost my data.
IMTLD said:
I just revived my mi5 using the test point method, it is rather simple actually.
Make sure you are using miflashtool beta,
I downloaded this rom china developer
I noticed that even though I chose save user data, I still lost my data.
Click to expand...
Click to collapse
Good to know it also worked for you, I just didn't believe that my battery was depleted from 70% just by hardbriking it...
After installing TWRP it asks to decrypt data even though I did not encrypt, hmmm what now
Edit:
I just did factory reset in TWRP and now I can see sdcard.
IMTLD said:
Hello everyone,
I have-or had- MI5 with latest cm14.1 on it, today I downloaded the latest rom from xiaomi.eu -Nougat-. I rebooted into recovery, wiped partitions, flashed the new rom, flashed successfully, and then flashed a font zip, the installer hanged at unmounting system for a long time, I forced rebooting it through holding power button the phone turned off and then never worked. nothing happens, no led when connecting to charger, pc does not recognize the phone at all, no sounds when connecting it. recovery and bootloader does not open. it is completely DEAD. Any help?
Click to expand...
Click to collapse
I also had my Mi5 die earlier today. Here's what I did to get it back:
1. Popped-open the back cover, removed the screws from the top panel
2. Disconnected battery (left side)
3. Connected battery back
4. Shorted the two contacts at the right side of the board
5. Plugged original USB in
Note that using a deep flash cable is a less intrusive way of doing steps 1-5, but that's what worked for me.
At this point, the PC detected the phone in EDL mode. I then attempted to flash the fastboot ROM for Mi 5, however, I kept getting errors about Missed Hello / Issue with COM port.
6. Downloaded an up-to-date version of Mi Flash (beta didn't work for me), disable Signature Enforcement (Windows 10) and install Qualcomm drivers
7. Downloaded a MIUI 7.5 fastboot rom
8. Flashed, got an error, about storage being not enough... But the screen turned on with the Mi logo. I was finally able to get the phone into Fastboot.
9. Successfully flashed MIUI 7.5 ROM using Mi Flash.
If you are still getting the COM port issue or Hello, try disconnecting the battery again and repeating steps 3-5.
Good luck.
idmissile said:
I also had my Mi5 die earlier today. Here's what I did to get it back:
1. Popped-open the back cover, removed the screws from the top panel
2. Disconnected battery (left side)
3. Connected battery back
4. Shorted the two contacts at the right side of the board
5. Plugged original USB in
Note that using a deep flash cable is a less intrusive way of doing steps 1-5, but that's what worked for me.
At this point, the PC detected the phone in EDL mode. I then attempted to flash the fastboot ROM for Mi 5, however, I kept getting errors about Missed Hello / Issue with COM port.
6. Downloaded an up-to-date version of Mi Flash (beta didn't work for me), disable Signature Enforcement (Windows 10) and install Qualcomm drivers
7. Downloaded a MIUI 7.5 fastboot rom
8. Flashed, got an error, about storage being not enough... But the screen turned on with the Mi logo. I was finally able to get the phone into Fastboot.
9. Successfully flashed MIUI 7.5 ROM using Mi Flash.
If you are still getting the COM port issue or Hello, try disconnecting the battery again and repeating steps 3-5.
Good luck.
Click to expand...
Click to collapse
Thanks for the reply, but I already fixed it this way. I used miflashtool beta since the final release did not work.
The problem is did you lose your data after the flash? because I lost mine even though I checked save data in miflashtool
IMTLD said:
Thanks for the reply, but I already fixed it this way. I used miflashtool beta since the final release did not work.
The problem is did you lose your data after the flash? because I lost mine even though I checked save data in miflashtool
Click to expand...
Click to collapse
At that point, I didn't really care if I lost data since I didn't have much on it anyway. Nice to hear that you got yours back. Those were dark hours, yes?
Thanks for giving a hope (checking way to recover from video). I'll get proper screwdrivers soon and try do the same.
I have narrowed down the issue, its the nougat firmware thats caused these recent issues. Xiaomi has distributed an unstable bootloader. I highly recommend reverting back to marshmallow firmware and OS
Shaky156 said:
I have narrowed down the issue, its the nougat firmware thats caused these recent issues. Xiaomi has distributed an unstable bootloader. I highly recommend reverting back to marshmallow firmware and OS
Click to expand...
Click to collapse
but how my mi5 now hardbricked no fastboot no recovery no edl
IMTLD said:
People reported it worked in xiaomi eu thread, gonna try once I have the tools, I wonder why the * dev didn't write "- NEVER wipe /system partition manually in your life!" before the download links
Click to expand...
Click to collapse
I can confirm that this 100% works for me. You need to be a bit patient with the tweezers and getting the contact points right. It didn't immediately work for me, and I think I had to try a dozen times at least. But eventually it did recognize it. Once MiFlash can see it, you need to use the latest China stable rom. I tried the latest china dev, but it kept on giving errors of missing hello packets.