After my phone bricked I installed latest Chinese Stable ROM in EDL mode. I chose EDL mode for two reasons (1. I suspected that the phone only works while plugged in to charge and 2. the EDL mode turns off the phone after flashing so I can plug in the charger before booting). Turns out I was right. After the flash was over I tried to boot it without charging it first and it didn't work. After I connected it to the charger it booted normally and the ROM installed successfully.
I tried it again this morning after it fully charged. Few seconds after Ii disconnected it, it turned off. When I tried to turn it back on it was just rebooting to the MI logo screen. I plugged it in the charger and it rebooted 2 times (both times it got to those three dots at the bottom of the screen) and the third time it booted normally.
I also just noticed that the phone is curved a bit (maybe less than 1mm difference between upper left edge and rest of them), maybe from wearing it in tight pockets or something like that.
I think your battery might be dead. Try checking the voltage or the quality.
Replaceable batteries are pretty cheap.
Trimis de pe al meu Mi-4c folosind Tapatalk
Might be faulty battery, might be bad kernel, might be anything. Best way to check is to try to flash latest dev china rom via fastboot, if it still doesn't work try flashing stable 5.1.1 rom, again, via fastboot. If none of the solutions above doesnt work might be bad battery or worse, the controller on mobo died.
timipisoboy said:
Might be faulty battery, might be bad kernel, might be anything. Best way to check is to try to flash latest dev china rom via fastboot, if it still doesn't work try flashing stable 5.1.1 rom, again, via fastboot. If none of the solutions above doesnt work might be bad battery or worse, the controller on mobo died.
Click to expand...
Click to collapse
Well I hope it's a battery, because I just bought one to replace it. What is that mobo controller? Is it replaceable?
I have the same issue,
Battery replacement and stock rom of android 7 didn't help
I'm afraid is another hardware issue /:
I do have a similar problem, flashed xiaomi.eu and something have been broken.
I dont know how and why but its very strange.
Unplugged from supply i can boot up the phone, can see the miui logo and boot into fastboot but NOT into recovery and not boot up os.
As soon as i plug in supply it works quit normally, can boot up everything seems to be working, booting into twrp and flashing rom. No problem at all.
If i unplug while running os it imediately shut down.
The battery bar inside twrp show strange jumps.
What happens did somehting break ? Id like to gift the phone my mother for christmas.
Danny94 said:
I do have a similar problem, flashed xiaomi.eu and something have been broken.
I dont know how and why but its very strange.
Unplugged from supply i can boot up the phone, can see the miui logo and boot into fastboot but NOT into recovery and not boot up os.
As soon as i plug in supply it works quit normally, can boot up everything seems to be working, booting into twrp and flashing rom. No problem at all.
If i unplug while running os it imediately shut down.
The battery bar inside twrp show strange jumps.
What happens did somehting break ? Id like to gift the phone my mother for christmas.
Click to expand...
Click to collapse
Hi how did you resolved this. Facing same problem. Will replacing battery solve this.
visharagp said:
Hi how did you resolved this. Facing same problem. Will replacing battery solve this.
Click to expand...
Click to collapse
I purchased a new battery and it was working normally again and still working.
Danny94 said:
I purchased a new battery and it was working normally again and still working.
Click to expand...
Click to collapse
Great then I have to purchase a new battery ss well
Related
I have the cricket model. Sometime last night my phone started rebooting on every ROM and kernel. Nothing I do will get it to stop. It doesn't happen in TWRP and that's it. I thought maybe it was a battery issue as I haven't been able to fully charge it because of this issue but that's not helping either. I've been trying to use the upgrade tool but in this state the computer never even recognizes the phone and I can't even get that far, plus it reboots even when in download mode. I'm about to call cricket and see if they can just send me a new one since I've only had it a week but is there anything I can do? Does anyone have a boot IMG for complete stock 60450 ?!? EDIT: Got the tool to recognize phone and start process but what do ya know phone reboots even deep into download mode. It just always wants to restart to the system for some reason, except for when on twrp. UPDATE:EDIT: Turns out the reason the upgrade app wasn't working is because i didn't have enough space for the update to download on the PC . I didn't realize because the app never stated why it was restarting my phone or disconnecting so I just assumed it was related to why my phone kept restarting on all ROMs. Wow lol I feel so damn stupid for not thinking of this 2 days ago. Its installing now and hopefully this fixes my reboot issues. Thanks to everybody here for helping and answering my 1000 question's on every post. Really appreciate it.
it looks like motherboard is gone. I hope you can return it when you have custom rom installed.
DallasCZ said:
it looks like motherboard is gone. I hope you can return it when you have custom rom installed.
Click to expand...
Click to collapse
I've had the phone for one week lol. Motherboard is gone? Could something be messed up in build prop somewhere? I did try to use a DPI changer app on stock rom once or maybe xposed? I've done a lot of flashing since I got it trying to find the perfect setup. I just noticed that the USB cable it came with is crap so now that I'm using a different one I'm hoping that low discalobrated battery was the issue. Charging it up proper and gonna see what happens after. Also for some strange reason the Flyme OS ROM is the only one that doesent seem to want to restart as often. It still does but it lasts a lot longer before doing so , why idk lol.
turn off the phone, charge it fully and then run the upgrade tool to go back to stock.
Odesláno z mého 6045X pomocí Tapatalk
DallasCZ said:
turn off the phone, charge it fully and then run the upgrade tool to go back to stock.
Odesláno z mého 6045X pomocí Tapatalk
Click to expand...
Click to collapse
I wasnt previously able to corectly charge becauss when i would turn the phone off to charge it wpuld power up instead of gking to the charging acreen. I think the USB cable that came with the phone might have been faulty and I just didn't notice it somehow. Now that I've charged the phone to 50% Flyme is up and running without a reboot, although running quite hot....which could also be the issue. Maybe the metal on the USB tip got toasted. That would explain my reboots in download mode but it doesent explain why the phone never once rebooted on me while in twrp and why it would reboot even while not being charged and had like 30%. Gonna charge it up to 100 and try the tool again.
carnivalrejectq said:
I wasnt previously able to corectly charge becauss when i would turn the phone off to charge it wpuld power up instead of gking to the charging acreen. I think the USB cable that came with the phone might have been faulty and I just didn't notice it somehow. Now that I've charged the phone to 50% Flyme is up and running without a reboot, although running quite hot....which could also be the issue. Maybe the metal on the USB tip got toasted. That would explain my reboots in download mode but it doesent explain why the phone never once rebooted on me while in twrp and why it would reboot even while not being charged and had like 30%. Gonna charge it up to 100 and try the tool again.
Click to expand...
Click to collapse
if you can boot to flyme, and got no reboots in TWRP i suggest you flash from TWRP your previously mad ebackup..if you dont have any, just flash stock kernel or look here in threads, there was a thread and it contains TWRP backup of stock rom..if you find TWRP backup of your STOCK 6045O then flash it from TWRP, and if you dont observe nay reboots, it was due to the kernel. IF it still reboots send it to warranty repair.
DallasCZ said:
if you can boot to flyme, and got no reboots in TWRP i suggest you flash from TWRP your previously mad ebackup..if you dont have any, just flash stock kernel or look here in threads, there was a thread and it contains TWRP backup of stock rom..if you find TWRP backup of your STOCK 6045O then flash it from TWRP, and if you dont observe nay reboots, it was due to the kernel. IF it still reboots send it to warranty repair.
Click to expand...
Click to collapse
Well I'm back on CM now with no reboots. I guess my USB cable just sucked and my battery calibration was off so the battery was showing more than it actually had and probably causing instability. However, I still can't get the tool to work. It just reboots at around 22% exiting me out of download mode. BTW I've searched and scowled almost every thread and I can't find a stock kernel. There's the arde one but I thought that was just his custom kernel for stock. And the twrp back up I definitely can't find. I seen the thread but there was no link.
carnivalrejectq said:
Well I'm back on CM now with no reboots. I guess my USB cable just sucked and my battery calibration was off so the battery was showing more than it actually had and probably causing instability. However, I still can't get the tool to work. It just reboots at around 22% exiting me out of download mode. BTW I've searched and scowled almost every thread and I can't find a stock kernel. There's the arde one but I thought that was just his custom kernel for stock. And the twrp back up I definitely can't find. I seen the thread but there was no link.
Click to expand...
Click to collapse
If it was the USB cable why is mobile upgrade tool rebooting the device at 22%? It makes no sense. It could be the pins on the usb socket on the phone or i dont know.
You should ask someone with the 6045O device to send you the boot.img (aka kernel) of stock 6045O.
DallasCZ said:
If it was the USB cable why is mobile upgrade tool rebooting the device at 22%? It makes no sense. It could be the pins on the usb socket on the phone or i dont know.
You should ask someone with the 6045O device to send you the boot.img (aka kernel) of stock 6045O.
Click to expand...
Click to collapse
Well I first noticed my cable was funky when I loaded up Flyme it kept making an unplug sound and I thought it was just the ROM glitching out but I changed the cable and it stopped. About the tool......I have a Windows tablet that it's only USB connection is one of those mini USB to full adapters and it's a little loose. I have zero problems with it plugging my phone into it for file transfer or for adb, it's all fine there so idk why it would be causing an issue with the tool, last time I tried it k specifically made sure all connections were sturdy and didn't move the whole time and it still rebooted. I noticed somebody in one of the threads said his device did the same thing though and that's why he couldn't use the tool as well......nobody ever replied to him lol
Ahh I spoke to soon. Restored my stock, because that's what I prefer for even at OC it still doesent make the phone nearly as hot as CM ROMs and the restarts came right back even with a decent charged battery. I'm back on CM again though and its not happening. Doesent make much sense because before the restarts were happening across all ROMs. It can't be the kernel in my stock restore as I had used it a bunch of times before with no issues...... Though it is saved on my external SD..... But so is the cm build I'm using. Idk whats going on here. Just wanna return the phone to full stock and call it a day lol. Edit: spoke to soon again lol. There goes CM rebooting, although it took way longer than stock to do so.
Hi all.
I have searched this forum (I know it's very frowned upon to start a thread without doing so) but the symptoms don't completely match my issue so I've resorted to asking.
I have a Nexus 5, which I was using as a hotspot, tethering to an Amazon fire stick, when it switched itself off.
It hasn't booted since, I've tried all possible button combinations for up to 2 minutes and still nothing.
If connected to a charger I get the white battery icon with the lightning bolt for a few seconds then blank screen, this will loop until unplugged.
When I have the battery icon on screen I can hold power button and it will display "Google" and vibrate as if starting to boot, then go blank again.
Have reinstalled original battery and the symptoms remain the same.
Am on marshmallow 6.0.1 totally stock am also out of warranty.
Any ideas would be greatly appreciated.
Thanks in advance.
Try to boot in bootloader mode if it boots connect to it comp and then unlock the bootloader if not and install latest Twrp if not then flash a custom rom and boot it then flash factory images .. Done. Back to Stock!
Try booting in bootloader mod while connecting it do the charger. (Wall charger )
pranavmali said:
Try to boot in bootloader mode if it boots connect to it comp and then unlock the bootloader if not and install latest Twrp if not then flash a custom rom and boot it then flash factory images .. Done. Back to Stock!
Try booting in bootloader mod while connecting it do the charger. (Wall charger )
Click to expand...
Click to collapse
Thanks for the suggestion but can't get into bootloader mode, it's only alive for about 3-4 seconds if plugged in then it goes off and then back to the white battery.
J_The_Nerd said:
Thanks for the suggestion but can't get into bootloader mode, it's only alive for about 3-4 seconds if plugged in then it goes off and then back to the white battery.
Click to expand...
Click to collapse
Mother board problem or change try changing ur battery... Surely Mother Board problem! Coz while u were connected to a hotspot and then u switched off it.. The battery would suddenly undervolt ur motherboard... And Undervolting id Very Very bad even if u change it from software or hardware...This had happen to my Sis nexus 5. .. So given it a chance changing the battery! Coz that helped Me.. But also try booting in bootloader mod and flashing twrp it will save couple of Bucks and Time
Press the thanks button if this helps
I would replace the battery first. It seems like the battery was completely drained while hotspotting.
Are you using the original USB cable and charger that came with the phone?
audit13 said:
I would replace the battery first. It seems like the battery was completely drained while hotspotting.
Are you using the original USB cable and charger that came with the phone?
Click to expand...
Click to collapse
Yes using the original charger, still does the same on power bank and old Samsung charger.
I'll give a battery swap another go.
pranavmali said:
Mother board problem or change try changing ur battery... Surely Mother Board problem! Coz while u were connected to a hotspot and then u switched off it.. The battery would suddenly undervolt ur motherboard... And Undervolting id Very Very bad even if u change it from software or hardware...This had happen to my Sis nexus 5. .. So given it a chance changing the battery! Coz that helped Me.. But also try booting in bootloader mod and flashing twrp it will save couple of Bucks and Time
Press the thanks button if this helps
Click to expand...
Click to collapse
If battery swap doesn't help is the motherboard easy to swap out? Providing I can find a replacement?
Motherboard is very easy to swap out.
Update, put original battery back in for the second time, first time didn't make a difference, possibly took longer this time. But all is good now.
Thanks to all
Hello, my problem is that exactly yesterday i turned my phone off
wanted to turn it on ,but it simply doesn't work
can't get it to recovery or the pc communication mode (i guess it's locked anyway, i don't know).
Thought it was battery, charged it to 100%, nothing.
Literally anything would help me.
.kyon said:
Hello, my problem is that exactly yesterday i turned my phone off
wanted to turn it on ,but it simply doesn't work
can't get it to recovery or the pc communication mode (i guess it's locked anyway, i don't know).
Thought it was battery, charged it to 100%, nothing.
Literally anything would help me.
Click to expand...
Click to collapse
can't get it to recovery or the pc communication mode:same but i can see batery icon when i plug on charger but not charge device
It happened to me also the phone no longer loads so I dismantle them check the motherboard(its ok ) and manually charge the battery because it had the problem of 0 volt
If nothing works for you just flash it
Constant boot loop even after flashing rom
My sony e3 gets in boot loop every one or two day even when i try to flash the stock rom or lineage, nitrogen one.
So basically i have to flash any of the rom every now and then to keep it running. Can anyone please suggest me a solution or at least tell me why this happens??
Did you do a wipe before flashing?
Sent from my Xperia E3 d2202 with nougat
Hello XDA Community and stuff,
i have a problem with my S7, which i flashed with Superman Rom a few weeks ago. It worked fine with all its functions, but this morning i woke up with my phone under my pillow. I guess its battery got completly drained out, because it was already low when i fell asleep. i tried charging it, but nothing happens. It also won't boot and the only thing that works, is Download mode. I tried Recovery mode, force reset, safe mode..... nothing works. I'm using TWRP recovery.
I would appreciate, if i could keep my app data, if not then i won't bother, since it can't be helped in my case, if there is no way of doing it without full wipe or anything.
PS: if my english is wrong or at any point not perfect, it may be because i am german.
with kind regards
ceiber
ClockWorkMod recovery?
Flash TWRP
*Detection* said:
ClockWorkMod recovery?
Flash TWRP
Click to expand...
Click to collapse
I am so stupid! i meant Team Win. sorry misleading info
Try flashing TWRP again, if it doesn't work, flash stock and start fresh to make sure it's not a hardware fault
*Detection* said:
Try flashing TWRP again, if it doesn't work, flash stock and start fresh to make sure it's not a hardware fault
Click to expand...
Click to collapse
It worked, but why? it started charging with charging indicator (battery symbol and lightning in the middle with green LED on bottom) after the flash was succesfull. Then i detached it and connected my normal charging cable in wall socket. I had to wait for 1% charge and then i was able to boot normally into my rom. Is there any explanation for that?
ceiber said:
It worked, but why? it started charging with charging indicator (battery symbol and lightning in the middle with green LED on bottom) after the flash was succesfull. Then i detached it and connected my normal charging cable in wall socket. I had to wait for 1% charge and then i was able to boot normally into my rom. Is there any explanation for that?
Click to expand...
Click to collapse
Sounds like recovery corrupted, maybe due to the battery running out if it didn't manage to shut itself down in time
My OnePlus one is only showing OnePlus logo screen and turning off, I flashed stock ROM through my computer as I thought it got soft bricked, nothing worked, when I connect it to the battery charger it shows battery charging, I guess there's some hardware problem, any suggestions will be helpful, thank you
Samruddhi123 said:
My OnePlus one is only showing OnePlus logo screen and turning off, I flashed stock ROM through my computer as I thought it got soft bricked, nothing worked, when I connect it to the battery charger it shows battery charging, I guess there's some hardware problem, any suggestions will be helpful, thank you
Click to expand...
Click to collapse
option 1 : Do a complete wipe in TWRP (system,data,cache,dalvik) and then flash the stock rom again.
option 2: use the "back to stock/restore soft bricked device" option on bacon root toolkit using your pc
If this dosen't work only then it could be a possible hardware issue.
i have the same problem, but it survived with a simple things.
Fully charged your phone,try installing twrp (i think the newest one) and try to full wipe data,and installing new rom.
I installed lineage os 14.1 everything work.
And if it still bootloop,try to replacement the battery, and fully charged. Then try flash twrp and new rom.
good luck
malcolmm21 said:
option 1 : Do a complete wipe in TWRP (system,data,cache,dalvik) and then flash the stock rom again.
option 2: use the "back to stock/restore soft bricked device" option on bacon root toolkit using your pc
If this dosen't work only then it could be a possible hardware issue.
Click to expand...
Click to collapse
I tried installing ROM through TWRP but when I used to start the installation the process used to suddenly stop and the device used to boot for no reason, and now it is not showing any recovery, I flashed stock recovery still nothing
bedgja said:
i have the same problem, but it survived with a simple things.
Fully charged your phone,try installing twrp (i think the newest one) and try to full wipe data,and installing new rom.
I installed lineage os 14.1 everything work.
And if it still bootloop,try to replacement the battery, and fully charged. Then try flash twrp and new rom.
good luck
Click to expand...
Click to collapse
Tried everything what you said except replacing the battery, it still shows OnePlus logo and turns off, guess the problem is with the hardware (battery or motherboard)
Samruddhi123 said:
Tried everything what you said except replacing the battery, it still shows OnePlus logo and turns off, guess the problem is with the hardware (battery or motherboard)
Click to expand...
Click to collapse
try to replacing the battery, cause many thread said the oneplus one always bootloop and back to normal when it charged or in power bank. i have tried and yup...replacement the battery is simple ways to check there is no problem with the board.
good luck