Hey guys,
after I have got some problems with charging in the past (wallchargers are always recognized as USB, very slow loading) I upgraded my OPO to CM13.
Now my phone does not charge anymore at all, all animations and charging recognitions seems to work (except wallchargers are still shown as USB), but the input current is always 0 mA, now I am stuck at 2% battery with power-save mode
Powering off and loading seems not to work, after powering on after some time battery is not increased
Ampere shows, that I am still losing 10-40mA with status discharging, but usb charger plugged
At the beginning (or afterI had noticed) I had Boeffla kernel and app, which showed, that input current massively drops from 250-400mA to 0 mA after one second charger plugged in. I tried to increase from stock logic to 1500mA, but same problem
MV stuck at ~3620mV
Does anyone know this problem?
Get a new Battery
So a broken battery causes a wrong detection of charger type, for example?
I am really wondering, if this is just a battery problem
I could load battery over night in TWRP with about 7-10% per hour, device was now full and mV was about 4230
Now powered on, decreases again
Atleast for me and a friend, only the original OPO AC Charger + Cabel gets reconized as AC Charger. Everything else, no matter what, is only a USB Charger with around 600mAh-800mAh max (Samsung Fast Charge AC Adapter 2000mAh which works on S5)
I don't belive that your IC Power Circit Chip is broken, in normal cases it would lead into a complete board dead. But yours still working, so it should be allright.
If you lucky its just the battery, I in your position would replace it anyway. Secound part to set the focus on is the USB Port, it can be damaged or just corroded over the time. So if you plan to setup a order buy the two parts.
tt might software problem. when u flash a new kernel and u forgot to wipe cache and dalvik , it sometimes make ur phone take more time to charge. (srry bad english)
Traace said:
Atleast for me and a friend, only the original OPO AC Charger + Cabel gets reconized as AC Charger. Everything else, no matter what, is only a USB Charger with around 600mAh-800mAh max (Samsung Fast Charge AC Adapter 2000mAh which works on S5)
I don't belive that your IC Power Circit Chip is broken, in normal cases it would lead into a complete board dead. But yours still working, so it should be allright.
If you lucky its just the battery, I in your position would replace it anyway. Secound part to set the focus on is the USB Port, it can be damaged or just corroded over the time. So if you plan to setup a order buy the two parts.
Click to expand...
Click to collapse
Thanks I will change battery first I think
As said, i could load over night to 100% (4230+mV) in TWRP, vey strange, the charging symbol in TWRP (the "+") was shown, currently I am trying the same again, but it seems not to load anymore right now
MojoManagement said:
Thanks I will change battery first I think
As said, i could load over night to 100% (4230+mV) in TWRP, vey strange, the charging symbol in TWRP (the "+") was shown, currently I am trying the same again, but it seems not to load anymore right now
Click to expand...
Click to collapse
Okay nice to hear. I advice to replace both. The USB part is just 5$ more ~ and its not that difficult. As for the battery, u have to open the opo anyway.
did you use battery calibration to clear the battery file after flashing?
I changed the battery and the usb connector with flex cable. Same issue.
Btw in my car the phone loads sporadically, but with about 1500mA, very very strange. I checked it again with 4 wall chargers and different usb cables, here it does not work
So it seems that I have to load the phone in my car.
Oneplus support has not been writing back for over a week.
Only the original charger and cable gets recognized as AC charger
KuranKaname said:
Only the original charger and cable gets recognized as AC charger
Click to expand...
Click to collapse
No, I got a few chargers and some of them were recognized as AC already. Anyway, the original one is not recognized as AC either.
My OPO is also not recognized by any computer anymore.. so no fastboot flash
Anyone got another idea what I could try?
MojoManagement said:
Anyone got another idea what I could try?
Click to expand...
Click to collapse
Hi, by advance sorry for my poor English.
Since you changed the battery it doesn't seem to be a material issue.
I don't really think that this will solve your problem, and you may want to keep using cm13, but you could try this :
-Make a nandroid backup and save all your data.
-Flash TWRP(2.8.6.0 !), you could either flash it or just boot the image via your computer if you want to keep stock recovery.
-Clean Flash Oxygen OS (oxygen_1.0.0_flashable.zip)
-Don't forget to do a factory wipe via TWRP, and reboot.
Then try the "OPO charging current" app, and see if it is charging above 800mA or not.
If oxygen OS doesn't work, you can try Calkulin's_Stock_OPO_XNPH44S_ROM_v1.0.zip
I'm running cm13 (114) nightly and I also have some charging issues, tough they are not as serious as yours.
<!> EDIT <!> : Before flashing another rom, you can try this, it significantly improved my charging speed over cm13 :
-Go to Settings -> Gestures and disable everything. Then reboot and try OPO charging current app.
MethylHaine said:
Hi, by advance sorry for my poor English.
Since you changed the battery it doesn't seem to be a material issue.
I don't really think that this will solve your problem, and you may want to keep using cm13, but you could try this :
-Make a nandroid backup and save all your data.
-Flash TWRP(2.8.6.0 !), you could either flash it or just boot the image via your computer if you want to keep stock recovery.
-Clean Flash Oxygen OS (oxygen_1.0.0_flashable.zip)
-Don't forget to do a factory wipe via TWRP, and reboot.
Then try the "OPO charging current" app, and see if it is charging above 800mA or not.
If oxygen OS doesn't work, you can try Calkulin's_Stock_OPO_XNPH44S_ROM_v1.0.zip
I'm running cm13 (114) nightly and I also have some charging issues, tough they are not as serious as yours.
<!> EDIT <!> : Before flashing another rom, you can try this, it significantly improved my charging speed over cm13 :
-Go to Settings -> Gestures and disable everything. Then reboot and try OPO charging current app.
Click to expand...
Click to collapse
As said, my OPO is not anymore recognized by usb at every computer.
So in case of any error, I could not flash anything with fastboot.
I am wary about flashing Oxygen OS in TWRP, also I have cm13 and caf things at phone
Oxygen OS 2.4.1:
Also, do not try to flash this build through TWRP. You will most likely lose your radio and IMEI which means a trip to our customer support. It won't lead to thermonuclear war but just don't do it.
Click to expand...
Click to collapse
I have TWRP 2.8.6.0 installed already and my problem existed with latest cm 12.1 nightly, with temasek 5.1.1 and latest cm13 nightly.
Only with sultanxda caf cm 13 charging works with plug-in delay and very slowly
MojoManagement said:
No, I got a few chargers and some of them were recognized as AC already. Anyway, the original one is not recognized as AC either.
My OPO is also not recognized by any computer anymore.. so no fastboot flash
Click to expand...
Click to collapse
So u changed the USB port and the OPO is not recognized at all anymore?, then u made something wrong, or the part is broken
MojoManagement said:
As said, my OPO is not anymore recognized by usb at every computer.
So in case of any error, I could not flash anything with fastboot.
I am wary about flashing Oxygen OS in TWRP, also I have cm13 and caf things at phone
Oxygen OS 2.4.1:
I have TWRP 2.8.6.0 installed already and my problem existed with latest cm 12.1 nightly, with temasek 5.1.1 and latest cm13 nightly.
Only with sultanxda caf cm 13 charging works with plug-in delay and very slowly
Click to expand...
Click to collapse
I though it could be okay since you bought a new cable.
The version of oxygen OS you're supposed to flash is, as I said, 1.0.0, not 2.4.1, and via twrp 2.8.6.0. This ain't supposed to cause your phone any harm (At least, it didn't caused me any trouble).
Also, this may be a stupid question, but were all drivers correctly installed on the computers with which you tried to detect your phone while in fastboot mode ?
Traace said:
So u changed the USB port and the OPO is not recognized at all anymore?, then u made something wrong, or the part is broken
Click to expand...
Click to collapse
It was already broken before, but I dont know the exact date and reason
I replaced the complete usb dock with cable to board and battery, same issue
MethylHaine said:
I though it could be okay since you bought a new cable.
The version of oxygen OS you're supposed to flash is, as I said, 1.0.0, not 2.4.1, and via twrp 2.8.6.0. This ain't supposed to cause your phone any harm (At least, it didn't caused me any trouble).
Also, this may be a stupid question, but were all drivers correctly installed on the computers with which you tried to detect your phone while in fastboot mode ?
Click to expand...
Click to collapse
Of course all drivers are here, the phone is not recognized at all, no windows sound when plugging in or any new device in device manager. Every other phone works here. I also tried 3 different computers
I read so many issues with Oneplus RMA... so I try everything else before
Edit: forgot to mention again, charging does not work in TWRP, too, so I dont think its an OS issue
Any one know oneline market where can i order opo power ic chip?
Related
Bootloader unlocked,. but in a boot loop with CWM Recovery. Battery too low to flash new recovery in via fastboot.
I assume those are GSM carriers? Might work, see below.
There is no developer edition of this device. They all have unlockable bootloaders - but you're not looking for that. You mean carrier unlocked... which the SIM in the Q is fixed, not 'user-accessible'....
There are folks in Europe who have hacked the device to put their own SIM in.
http://forum.xda-developers.com/showthread.php?t=1929143
Good luck.
Hi thanks for the reply, yes I was hoping to use it on GSM (Fido), but wouldn't mind CDMA/LTE/etc so long as it works.
got the bootloader unlocked using motopocalypse.
Oops. Tried flashing CM10.1.3 and on reboot it hung at the CM logo. Also have CM11's zip on the sdcard, but it fails installing (error 7). Can't seem to push any files onto it using adb.
edit: now its mostly staying with the screen off and the green light..sometimes I get the "warning:bootloader unlocked" screen.
edit: i let it sit for a while and it wound up in CWM. still cant see it with adb though.
adrienspawn said:
Oops. Tried flashing CM10.1.3 and on reboot it hung at the CM logo. Also have CM11's zip on the sdcard, but it fails installing (error 7). Can't seem to push any files onto it using adb.
edit: now its mostly staying with the screen off and the green light..sometimes I get the "warning:bootloader unlocked" screen.
edit: i let it sit for a while and it wound up in CWM. still cant see it with adb though.
Click to expand...
Click to collapse
Flash an updated version of recovery in fastboot mode (TWRP 2.6.3.1: http://goo.im/devs/OpenRecovery/asanti/openrecovery-twrp-2.6.3.1-asanti_c.img ), go to recovery and flash your CM11 zip.
AndyYan said:
Flash an updated version of recovery in fastboot mode (TWRP 2.6.3.1: http://goo.im/devs/OpenRecovery/asanti/openrecovery-twrp-2.6.3.1-asanti_c.img ), go to recovery and flash your CM11 zip.
Click to expand...
Click to collapse
When I was able to get into fastboot with adb it said the battery was too low to flash a new recovery. now i cant use adb as its not detected...
adrienspawn said:
When I was able to get into fastboot with adb it said the battery was too low to flash a new recovery. now i cant use adb as its not detected...
Click to expand...
Click to collapse
...Just charge the battery when powered off?
Sent from Google Nexus 4 @ CM11
AndyYan said:
...Just charge the battery when powered off?
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
when I let it charge now all I get is the warning:bootloader unlocked screen with the ability to manually shut it down/restart but cant seem to enter recovery or fastboot.
This happens when you use a faulty cable/charger. Try a Motorola cable and charger if you have. If you do, try a different cable.
I've had this problem several times. Always with a defective/non-Motorola-compliant cable and/or charger.
The Micro USB cable that came with my Powerbank does this and a 5V USB charger that came with a no-name camera. But also a Philips 2.1A USB charger.
So again, try a different, preferably original, charger and/or cable and hopefully you will be fine.
Die Bruine said:
This happens when you use a faulty cable/charger. Try a Motorola cable and charger if you have. If you do, try a different cable.
I've had this problem several times. Always with a defective/non-Motorola-compliant cable and/or charger.
The Micro USB cable that came with my Powerbank does this and a 5V USB charger that came with a no-name camera. But also a Philips 2.1A USB charger.
So again, try a different, preferably original, charger and/or cable and hopefully you will be fine.
Click to expand...
Click to collapse
You're right! Thanks for your time. I was using one that I had for my HTC G2, and the one that came with it (eBay) I assumed was Motorola's but taking a closer look it does look generic. Tried a blackberry 1.8A(highest) charger to bring the battery to full charge and successfully got into fastboot to flash twrp and then cm11.
Hello Everyone,
I'm new to this forum.
I have encountered a recent problem with my nexus 5.
I plug in the phone with the original charger (and many others), but it does not charge. When I go to the batery management options, it says "Not Charging". The phone nevertheless detects the charger which is plugged in, and the battery remains constantly at 65 percent while plugged in (but does not charge).
I have also tried plugging it via usb (the computer detects the phone, and I can even transfer files).
I have also tried with a wireless charger, and still get "Not charging".
I have attached a screenshot.
Thank you very much for your help.
Edit // Im runing on andrioid 4.4.4
About the simplest thing to do is to just backup your apps with titanium backup and flash the stock firmware with fastboot. Wiping system before flashing. And anything else. Just don't wipe userdata. (talking about with fastboot... Not recovery)
And make sure it works or not before reinstalling apps.
If not, it has to be hardware. Battery bad, or cable or charger, or charging port. Just cause data transfer still works doesn't mean the charging pins aren't damaged.
KJ said:
About the simplest thing to do is to just backup your apps with titanium backup and flash the stock firmware with fastboot. Wiping system before flashing. And anything else. Just don't wipe userdata. (talking about with fastboot... Not recovery)
And make sure it works or not before reinstalling apps.
If not, it has to be hardware. Battery bad, or cable or charger, or charging port. Just cause data transfer still works doesn't mean the charging pins aren't damaged.
Click to expand...
Click to collapse
Ok. This is the first time I will do it. Hope I don't brick my phone.
Should this guide helpo me solve the problem?
http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=198886316
ionetto said:
Ok. This is the first time I will do it. Hope I don't brick my phone.
Should this guide helpo me solve the problem?
http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=198886316
Click to expand...
Click to collapse
That's great info on fastboot. There is this guide here as well...
http://forum.xda-developers.com/showthread.php?t=2513701
It's not easy to brick a Nexus... Follow the instructions, flash the proper files and you'll be fine. ?
KJ said:
That's great info on fastboot. There is this guide here as well...
http://forum.xda-developers.com/showthread.php?t=2513701
It's not easy to brick a Nexus... Follow the instructions, flash the proper files and you'll be fine. ?
Click to expand...
Click to collapse
Great Thread. Seems foolproof.
Should I have any questions, I'll be bothering you again!
Thank you! :good:
Hi everybody,everything is in the title : my phone doesnt boot up anymore since the battery went to 0% I tried with different cable and adaptators. The problem appeared since i flashed boeffla kernel 4.0 u600 the phone detected the cable but the phone wasn't charging now i've made the error to not flash another kernel before the phone stopped.
Is there a solution different from changing the battery to boot up the phone and flash the phone with a stock kernel .When i plug the phone to the computer it's detected as unknow device but nothing more
What device?
Samsung or something else?
Oneplus one
PS : No recovery mode or any other available
mohamed13014 said:
Hi everybody,everything is in the title : my phone doesnt boot up anymore since the battery went to 0% I tried with different cable and adaptators. The problem appeared since i flashed boeffla kernel 4.0 u600 the phone detected the cable but the phone wasn't charging now i've made the error to not flash another kernel before the phone stopped.
Is there a solution different from changing the battery to boot up the phone and flash the phone with a stock kernel .When i plug the phone to the computer it's detected as unknow device but nothing more
Click to expand...
Click to collapse
Maybe use fastboot? The kernel shouldn't affect charging, only rate, as the phone on "off", just like the radio, operates on a different firmware, so it should still charge. The computer is seeing it, so fastboot into an oem unlock should be good. Install adb and what not.
Had similar experience with my old samsung note 2. Falshed a kernel with bug and then couldn't boot up. Then battery went down and phone refused to charge. But with note 2 you can always change battery.
Anyway maybe you need to tear down your phone and charge your battery, since it's hard to say if your phone is hard bricked because the battery ran out. Maybe you can try this thread which tells you how to fix a hard bricked oneplus one. https://forums.oneplus.net/threads/solution-recover-from-hard-bricked-oneplus-one.104943/
After a while without touching it, it finally charged, vert slowely, but it charged. I'll try to figure out what's the problem...
mohamed13014 said:
After a while without touching it, it finally charged, vert slowely, but it charged. I'll try to figure out what's the problem...
Click to expand...
Click to collapse
Mostly the Battery itself
If a battery is completely emtpy for a while it can just break. Its that simple.
Hi forum,
Basically a couple of days ago my S6 stopped fast charging and was charging at a very slow pace (~5% idle/hour) and have tried pretty much all the things on the internet (safe mode, checking for lint, toggle in settings, etc.) before as a last resort doing a factory reset. It also decided that it would not be picked up by the PC properly and showed as a malfunctioning device by device manager which I overlooked a little bit, as I assumed it was a software problem.
Anyways, after doing a factory reset through TWRP my phone can no longer boot to the operating system and now instead boots to TWRP. I have read online that I'd be able to flash firmware/files through Odin to fix the problem, however my phone does not get picked up by the PC so that's not an option for now, I've tried going into download mode also which it allowed me but it's still not recognised and I cannot boot to safe mode. Is there anything else I can try? I have tried restoring my boot and system partitions but still the same problem. The only thing I can think of is to try and find some more lint in the charger port to try and fix the USB if its a hardware problem still, as the S6 doesn't have removable storage so I can't bring any files over.
It will be fun seeing the expressions on the Samsung guys' faces when I walk in with a TWRP boot loop asking for a USB repair on warranty
Hope someone can help
I had issues charging too and it turned out to be my USB cable. Have u tried other cables?
Tapatalked yah
joppz said:
I had issues charging too and it turned out to be my USB cable. Have u tried other cables?
Tapatalked yah
Click to expand...
Click to collapse
Yes I've tried about four cables and two fast charge bricks however that is no longer the primary problem, from what I can see I need to figure out how to get the charger port working so I can flash or find something within TWRP to fix the boot.
Thanks though :highfive:
If we focus on just getting un boot looped I have a backup of my system and boot partitions from about a month ago and I tried restoring these to the device to help boot up, as far as I'm aware deleting the other partitions wouldn't help? Does anyone know which partitions are required for the system to run? And I'm going to try and see if there is an incompatibility with the drivers on windows otherwise I suspect a hardware issue. Looked online and the average cost for the usb port to be replaced is ~£150, which I may have to do as I'm rooted and therefore out of warranty. Would be great if TWRP could transmit files over wifi or had its own file downloader but I guess not everyone is on a bootlooped s6 with no SD card slot for transferring files and with USB problems :cyclops:
Any more ideas? Am I bricked indefinitely until the USB port is fixed??
From last 2 weeks I have been struggling with getting my mi4 to work again. Earlier, I was running AOSP Extended Custom Rom based on ANDROID 10 without root but bootloader unlocked since last 3+ years and It was running well. Following complication happened suddenly without installing any new app on my phone:
My payment app shown that my phone is rooted and did not let me do any payments
Unable to connect to WIFI showing password cannot be saved
After that, I tried cleaning apps cache while system was on and through TWRP recovery cleaned Dalvik cache and cache but that did not change any behavior.
Instead of factory resetting and reinstalling same rom, I was looking for new rom and found Xtended XR Vanilla ANDROID 11 rom unofficially released in following thread:
Xtended XR Vanilla ANDROID 11 For Mi4 (Cancro)
I downloaded this rom and Gapps from BitGapps as somehow LiteGapps was not installing playstore even it stated in the information. I tried installing Xtended XR and Gapps but TWRP stated Storage is insufficient. So, I decided to see if only Xtended XR rom works or not? It worked after reinstalling. Everything was working fine but battery was draining fast that was unusual because earlier it was giving me around 1.5-2 hours of Screen on Time and now it was down to around 40-50 mins! In order to get Google Playstore, I had to resize system partition.
After reading few articles, threads and watching YouTube videos, I deleted cache, system, data and vender partitions and resized and recreated them. But after doing that still twrp was showing the same message of storage but I found that it is a problem with many custom roms but can be solved by unmounting system, resize system and mounting system again from twrp after flashing rom. It worked and I was able to install BitGapps and except battery draining everything worked. Therefore I was thinking of flashing some custom kernel for battery draining as I was using CraneWing kernel with AOSP Extended it was working fine. Before that I started setting up my phone settings and installed apps from playstore.
Everything was fine till now but on next day after finishing all basic settings and installing apps, I encountered new problem. It happened twice whenever I try to change brightness manually phone restarts automatically. From second time onward phone stopped booting to system.
I tried following things that did not work:
Re-flashing Xtended XR Rom and BitGapps (installed successfully every time but didn't boot)
Wiping and Formatting cache, data, and system partitions
Changing TWRP version
Installing Stock Fastboot MIUI Global Rom for Mi4 Cancro (installed 4-5 times successfully via PC on fastboot, MI recovery opened twice but system did not boot)
Re-flashing TWRP again (Because battery was not charging, so whenever I keep phone as it is for like 1-2 days for draining battery I can open TWRP with 1-3% battery and can charge till 16-20% then it goes to boot loop with Mi Logo)
By this time I was only able to access Fastboot, so tried installing stock rom but it did not boot. Recovery is also not accessible. I found that I can flash stock rom in EDL mode. My phone does not support EDL from fastboot. Then I found following thread for reboot to edl via fastboot:
Reboot to EDL Via Modified Fastboot For Redmi Note 3
I used that but because it was for Redmi Note 3 and I think I made a mistake by using that. I tried button combinations of Power and Volume buttons and also tried battery draining but that did not work. Now at this moment I am stuck with following problems in given order to make my phone work again:
Battery not charging
Stuck in EDL Mode. Restarting frequently (in 2-3 seconds) in EDL continuously without system recognizing it as Qualcomm Device
Able to turn on Fastboot when Connect with Wall Charger but cannot with USB connected with PC. Though I can turn on Fastboot with wall charger connected and then connect to PC to perform any fastboot commands.
Custom Recovery not accessible (Can flash recovery but not opening)
I am not sure it is entirely battery problem or something wrong with custom rom, gapps or fastboot miui stock rom. I am not sure how can I solve this problem now. Battery replacement seems one thing that I can do but the company stopped manufacturing batteries but I found someone who has 3 years old battery stock and says it works very well for this and many other devices batteries that he sells even if manufactured batteries kept unused for long.
What should I do? I would appreciate if someone help me on this.
Thanks.
I think your brightness problem reason was that you flash cuatom kernel. I think that kernel not supported android 11. You should just tried other custom roms like havoc lineage for android 11 or etc.
Does it have blink red LED When you plug your device to charger?
It should turn to fastboot when you plug via USB to PC and hold vol up + power... Anyway, use another cable (original is better) to do that.
If u can't do that :
So about battery, for your problem i think you have 2 ways:
1. Buy and Change battery and flash fastboot rom and...
2. Charge your battery and flash fastboot and...
Just plug your device for 6-8 hours to the charger and after that, flash fastboot...
Be careful that you should use original cable.
moj.enjoy said:
I think your brightness problem reason was that you flash cuatom kernel. I think that kernel not supported android 11. You should just tried other custom roms like havoc lineage for android 11 or etc.
Does it have blink red LED When you plug your device to charger?
It should turn to fastboot when you plug via USB to PC and hold vol up + power... Anyway, use another cable (original is better) to do that.
If u can't do that :
So about battery, for your problem i think you have 2 ways:
1. Buy and Change battery and flash fastboot rom and...
2. Charge your battery and flash fastboot and...
Just plug your device for 6-8 hours to the charger and after that, flash fastboot...
Be careful that you should use original cable.
Click to expand...
Click to collapse
Actually, I did not flash any custom kernel with Xtended XR rom I was just thinking about finding compatible kernel later and then flash it.
Yes, I do get red LED but phone is continuously in EDL bootloop either I put on charge or connect with PC. With charger I can turn on fastboot but with PC it remain stuck in EDL. So I can perform some fastboot commands via getting fastboot by connecting charger -> turn on fastboot -> plug into PC. But after restart it remain in EDL bootloop. So exiting EDL is first major problem that I need to solve.
Your other two suggestions would not work if I cannot get out of EDL bootloop. Though I do think changing battery after resolving EDL bootloop can work but as of now I have no luck. I hope you get my point.
is there a way to manually stopping EDL via opening phone and do something with the motherboard or battery?
btw you have made a great rom @moj.enjoy thank you. I only got to use it for sometime but I liked it. I am planning to install the same rom if my phone starts.
Click to expand...
Click to collapse
maxrajgor said:
Actually, I did not flash any custom kernel with Xtended XR rom I was just thinking about finding compatible kernel later and then flash it.
Yes, I do get red LED but phone is continuously in EDL bootloop either I put on charge or connect with PC. With charger I can turn on fastboot but with PC it remain stuck in EDL. So I can perform some fastboot commands via getting fastboot by connecting charger -> turn on fastboot -> plug into PC. But after restart it remain in EDL bootloop. So exiting EDL is first major problem that I need to solve.
Your other two suggestions would not work if I cannot get out of EDL bootloop. Though I do think changing battery after resolving EDL bootloop can work but as of now I have no luck. I hope you get my point.
is there a way to manually stopping EDL via opening phone and do something with the motherboard or battery?
Click to expand...
Click to collapse
I know what you are say. But are u sure that you are in EDL mode?
I think when you charge battery, it can automatically bypass EDL! In my opinion charge your battery 8 hours and don't touch that. After that
moj.enjoy said:
I know what you are say. But are u sure that you are in EDL mode?
I think when you charge battery, it can automatically bypass EDL! In my opinion charge your battery 8 hours and don't touch that. After that
Click to expand...
Click to collapse
Alright, let me charge battery for 8 hours and then I will post here whatever happens.
maxrajgor said:
Alright, let me charge battery for 8 hours and then I will post here whatever happens.
Click to expand...
Click to collapse
I tried charging battery for 8 hours, but phone remain uncharged. Sadly, nothing changed.
While charging with charger, the red LED blinks variably between 3-12 times before showing MI logo in bootloop.
Blinking of red LED is the same when connected with PC, but in PC it remains in blinking and neither show MI logo nor allow me to fastboot. Also I hear connect and disconnect Windows OS sounds for devices frequently.
Its
maxrajgor said:
I tried charging battery for 8 hours, but phone remain uncharged. Sadly, nothing changed.
While charging with charger, the red LED blinks variably between 3-12 times before showing MI logo in bootloop.
Blinking of red LED is the same when connected with PC, but in PC it remains in blinking and neither show MI logo nor allow me to fastboot. Also I hear connect and disconnect Windows OS sounds for devices frequently.
Click to expand...
Click to collapse
I think It's battery issue...
CONCLUSIONI changed battery then able to flash custom rom, gapps and installed apps. It was working fine.
But again after few hours it suddenly went to bootloop and never booted again. Technician said there is some problem with PCB and phone is considered dead now.
Thank you @moj.enjoy for giving your time here.