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.
Related
Hi, I'm using Zeus Build 6, all was going well till yesterday. while plugging for charge show the charging symbol but instead it just depleted my battery (the number % shows on the battery)
restarted the phone, cleared battery status but nothing happen, Even tried with USB , but same thing.
It did happen in past, I just did a factory re-set and all worked fine after then.
writing here to see if i can do something to find out what exactly happening. I'm also not able to connect my phone to computer as usb connection option is not appearing. (tried with diff port/wire).
Any insight, direction where to head.
[right now i'm on 20% battery I'll wait till 10% then will do another factory reset to see if it solve]
Thanks.
I'm assuming you weren't using your phone while charging.
I believe it is the kernel. I had this problem with Entropy's daily driver before. It is just a bad flash. Try going back to stock and re-root. Then, flash Zeus (comes with infusion kernel). After that, flash another kernel via Odin (SGS Kernel Flasher gave me problems before).
Hope that helps.
Sent from my SAMSUNG-SGH-I997 using xda premium
Thanks for the reply, Yes I do not use phone while charging. I believe that kernal problem because when ever i switch off my phone and connect charger or usb cable it automatically get switch on every time. Simply flashing zeus again (wipe all things) will do ? is it necessary to go back to stock?
If i flash any rom that means Kernal too will be flashed with that ?
I advice you to do this:
- Go back to stock
- Flash Zeus (Zeus comes with Infusion Kernel which may have caused the problems)
- if problem still persists, flash another kernel through either CWM or Odin
Return to stock and do complete restore to hopefully clear the borked areas of the bad flash you seemed to have.
You can try to just reflash Zeus, but I cannot guarantee that will work as that already happened to me. As much as possible, use Odin to flash kernels.
Sent from my SAMSUNG-SGH-I997 using xda premium
Crinkypops said:
I advice you to do this:
- Go back to stock
- Flash Zeus (Zeus comes with Infusion Kernel which may have caused the problems)
- if problem still persists, flash another kernel through either CWM or Odin
Return to stock and do complete restore to hopefully clear the borked areas of the bad flash you seemed to have.
You can try to just reflash Zeus, but I cannot guarantee that will work as that already happened to me. As much as possible, use Odin to flash kernels.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
still a noob here lol but what does switching kernels do to my phone? ive done it a few times before and sometimes i get stuck on the samsung logo and sometimes the kernel flash does work but i dont notice ANY difference at all
SayDfuse said:
still a noob here lol but what does switching kernels do to my phone? ive done it a few times before and sometimes i get stuck on the samsung logo and sometimes the kernel flash does work but i dont notice ANY difference at all
Click to expand...
Click to collapse
I am no tech-geek, but I think that kernels are the ones responsible for the boot; overclocking; undervolting; and everything else that is needed to keep the phone going. ROMs are kind of just "like an Operating System" but not really.
Think of it as the ROM being the car and the kernel being the engine as it is responsible for the running of the processor and what not.
Don't quote me on anything, but that is my attempt. As I've said, I am no tech geek and please correct me if I'm wrong.
Sent from my SAMSUNG-SGH-I997 using xda premium
Ok I flashed
Just flashed again, 1 Hemidal back to stock, 2 Hemidal Entropy kernal to get Red CMW.
3 does the cleaning 4 flashed Aeon.
Now charging is fine but still facing problem in usb connection to phone. some time it got recognized some time not. already changed the cable/port but problem persist.
[ In going from Step 1 to Step 2 you may find problem while putting your phone in download mode, In that case just download ADB, put phone setting->debug mode enabled connect with usb and run "adb reboot download" from command prompt it will do the trick ]
rainbow99984 said:
Just flashed again, 1 Hemidal back to stock, 2 Hemidal Entropy kernal to get Red CMW.
3 does the cleaning 4 flashed Aeon.
Now charging is fine but still facing problem in usb connection to phone. some time it got recognized some time not. already changed the cable/port but problem persist.
[ In going from Step 1 to Step 2 you may find problem while putting your phone in download mode, In that case just download ADB, put phone setting->debug mode enabled connect with usb and run "adb reboot download" from command prompt it will do the trick ]
Click to expand...
Click to collapse
your usb on phone could be loose...? hardware issue...
rainbow99984 said:
Hi, I'm using Zeus Build 6, all was going well till yesterday. while plugging for charge show the charging symbol but instead it just depleted my battery (the number % shows on the battery)
restarted the phone, cleared battery status but nothing happen, Even tried with USB , but same thing.
It did happen in past, I just did a factory re-set and all worked fine after then.
writing here to see if i can do something to find out what exactly happening. I'm also not able to connect my phone to computer as usb connection option is not appearing. (tried with diff port/wire).
Any insight, direction where to head.
[right now i'm on 20% battery I'll wait till 10% then will do another factory reset to see if it solve]
Thanks.
Click to expand...
Click to collapse
Hey There,
We had the same issue with many units and solved all by doing the following:
-Flashing the unit back to stock
-Performing a factory data reset after flashing(This is a must)
Note: Even though your device will not connect to the computer in PDA mode you should still be able to connect in download mode so it can be flashed with ODIN.(Unless if it's hardware related)
I flashed a Jellybean touchwiz rom for Verizon GS3, and went to reboot and now nothing, zero zip nada. No charging led light, no way to get into recovery and no response.
Anything I can do?
what happens when you do vol up + home+power button?
Absolutely nothing. I tried to get back into the recovery to see if I could restore my backup and nope.
did you try leave it pluged in for 30mins ?
does it vibrate once when you try to turn it on?
No vibrating and no sign of life at all. Even when plugged into my computer, I was going to try the unbrick guide but it listed that I should be able to get into the recovery still.
NickTheMajin said:
No vibrating and no sign of life at all. Even when plugged into my computer, I was going to try the unbrick guide but it listed that I should be able to get into the recovery still.
Click to expand...
Click to collapse
leave it plugged in for a while to make sure its not drained battery
do you have a usb jig?
I don't have a USB jig but this is possibly good news. I removed the battery and SD card and plugged it into my computer and it tried to install drivers (failed but tried) and the led light comes on red.
if your gettin led now you more then likely need to let it charge
It doesn't give me the led with the battery in
Plug it into a wall charger for at least 30 or even better if you can get a battery from someone.
Sent from my sexy white Eclipsed galaxy S3
I think its gone still nothing.
red led means qualcomm download mode. sounds dead to me
Yeah, haha. I saw it and mentally prepared myself for it. Literally just got the phone today so Verizon had no qualms with just sending me a new phone. Guess I'm reactivating my Rezound in the meantime. Thanks for the help guys.
you know
I am surprised. That also happened to me the first time i flashed that very same rom (touchwiz) with twrp . I have done this so many times , i literarily can flash a rom on the way to work .
I was in shock , i still dont know how the heck can i flash a rom and brick .
I plugged mine into windows and i got the device manager driver error from hell . and my phone never came back up again
I stayed away form twrp and touchwiz and i still cant possibly comprehend how a simple rom flash can brick my phone .
Which ROM did you flash?
Sent from my SCH-I535 using xda premium
you could probably send it to get Jtag'ed for around $60 if your warranty is invalid (ie used device)
You just hard bricked it. I did the same thing. Check here - post 5 shows the same symptoms :http://forum.xda-developers.com/showthread.php?t=1770341
And here: http://forum.xda-developers.com/showthread.php?t=1791721
I was pushing a copy of root66 that I hadn't md5'd. Took a JTAG to bring me back (twice) .
Sent from my SCH-I535 using xda app-developers app
So, in the future, md5 checksum absolutely everything since I'm assuming now that that is why this happened? (Since I made doubly sure I was flashing a rom for my phone).
If you still have the file you downloaded, you can check it. That would answer that question. If it checks out fine, then we have to look elsewhere for the problem.
BTW, MobileTechVideos.com can bring you back - based on my experience with them, I highly recommend.
Sent from my SCH-I535 using xda app-developers app
Please share exactly what you did so others can benefit from your unfortunate experience.
What ROM did you flash?
Did you use ODIN or a recovery?
If recovery, which one - CWM or TWRP?
Was there any unusual condition you can think of ... low battery, USB connected to computer or to charger, etc?
So i was running cm10 and i wanted to install a kernel. I when to install and kernel via rom manager.. When i tried to install in the screen went black and i havent been able to get the phone to turn on since,,,, i noticed when i try to put the phone into dload mode nothing happens... When i plug the phone into the wall charger the led light turns on as if it was charging but i dont have the battery in.. If i put the battery in and i push the volume down home and power nothing happens...can someone please help??? Please!!!!!!!!! I think the kernel was something like k74 something like that...
If you arent able to get into download mode, or even get a vibrate out of the phone, then sadly it may be hard bricked. I don't understand how flashing a kernel could hard brick the phone, though. At any rate, worst case scenario is you will have to send the unit in for a JTAG repair if you are unable to get it to boot in any way.
bakerboy81 said:
So i was running cm10 and i wanted to install a kernel. I when to install and kernel via rom manager.. When i tried to install in the screen went black and i havent been able to get the phone to turn on since,,,, i noticed when i try to put the phone into dload mode nothing happens... When i plug the phone into the wall charger the led light turns on as if it was charging but i dont have the battery in.. If i put the battery in and i push the volume down home and power nothing happens...can someone please help??? Please!!!!!!!!! I think the kernel was something like k74 something like that...
Click to expand...
Click to collapse
Welcome to AOKP/CM. lol Wouldn't use rom manager myself but hold on a few and Droidstyle or Annoying duck should chime in soon. I don't remember how bricked that means. Maybe able to leave battery out awhile and get it back.
apacseven said:
If you arent able to get into download mode, or even get a vibrate out of the phone, then sadly it may be hard bricked. I don't understand how flashing a kernel could hard brick the phone, though. At any rate, worst case scenario is you will have to send the unit in for a JTAG repair if you are unable to get it to boot in any way.
Click to expand...
Click to collapse
i have never heard of jtag... can you give me more info just in case
JTAG is the only way to recover from a hard brick. It is a service that is performed by only one (or maybe a few) companies in the world for the S3 (and many many other devices). Heres a link to the service, which starts at $60, and a link to the video of the S3 being unbricked.
https://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/
https://www.youtube.com/watch?v=XnA8Djs55Ds&feature=player_embedded
Try leaving the device plugged into the charger for a hour or so then try to get into odin mode...if still nothing then it sounds like you flashed a kernel that was for the international s3.
bakerboy81 said:
So i was running cm10 and i wanted to install a kernel. I when to install and kernel via rom manager.. When i tried to install in the screen went black and i havent been able to get the phone to turn on since,,,, i noticed when i try to put the phone into dload mode nothing happens... When i plug the phone into the wall charger the led light turns on as if it was charging but i dont have the battery in.. If i put the battery in and i push the volume down home and power nothing happens...can someone please help??? Please!!!!!!!!! I think the kernel was something like k74 something like that...
Click to expand...
Click to collapse
Did you install the 10/14 nightly? I noticed that when I installed the 10/14 nightly and then installed leankernel over that my phone would no longer boot. A simple flash back to M2 and leankernel fixed the issue. 10/14 had a lot of kernel updates so I think that's the problem.
VolUp+Home+Power to boot back into recovery I believe.
Do all of your flashing manually in the future. ROM Manager = no.
Sent from my SCH-I535 using Tapatalk 2
Anayalata said:
Did you install the 10/14 nightly? I noticed that when I installed the 10/14 nightly and then installed leankernel over that my phone would no longer boot. A simple flash back to M2 and leankernel fixed the issue. 10/14 had a lot of kernel updates so I think that's the problem.
VolUp+Home+Power to boot back into recovery I believe.
Click to expand...
Click to collapse
Since his phone wont even power on it will be impossible to flash another ROM.
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thanks
FNM
bakerboy81 said:
So i was running cm10 and i wanted to install a kernel. I when to install and kernel via rom manager.. When i tried to install in the screen went black and i havent been able to get the phone to turn on since,,,, i noticed when i try to put the phone into dload mode nothing happens... When i plug the phone into the wall charger the led light turns on as if it was charging but i dont have the battery in.. If i put the battery in and i push the volume down home and power nothing happens...can someone please help??? Please!!!!!!!!! I think the kernel was something like k74 something like that...
Click to expand...
Click to collapse
Delete please
Sent from my PC36100 using Tapatalk 2
I am so sad as I write this...:crying:
I had TWRP custom recovery and running the ARHD 9.0 rom.
I was tempted to try the other roms so I played around with Omega and ReVolt rom..they worked fine...
Then, when I tried to reflash ARHD 9.0, I could get to TWRP recovery but it just reboots even before any of the buttons appear.
So, I went into download mode and flashed HighOnAndroid custom recovery.
It seem to work fine....so I went ahead and flashed ARHD 9.0....It installed fine and completed successfully.
But when I rebooted the device...sigh...no power, not even the charging animation when I plug it into the charger...
So, if anyone has a solution on what I should do, please do tell me or I am really sad...so so sad...:crying:
Try a different charger, cable and wall outlet. Leave the n8000 there for a while. Hold the power button for a while, then let it go. Listen closely to the speakers for the little samsung sound when it turns on. Idk if the rom you installed has a boot sound tho. Anyways, if you still dont have an answer after that.. I would maybe start to think the power button is dead. Its a last ditch option but plausible i suppose lol.
Beyond that, you might have to think about sell it for parts.
Oh and i remember from my time with the Samsung vibrant that sometimes, even if nothing comes up on the screen, the device might be picked up by Odin after doing the dl mode button combo
Sent from my Nexus 4 using xda app-developers app
younix258 said:
Try a different charger, cable and wall outlet. Leave the n8000 there for a while.
Click to expand...
Click to collapse
I brought a friend's Note and charged using my usb charger/cable...it is working ok.
I would maybe start to think the power button is dead. Its a last ditch option but plausible i suppose lol.
Beyond that, you might have to think about sell it for parts.
Click to expand...
Click to collapse
My Note is about 2 months old and is still under warranty period. As a last resort, I can send it to them.
Oh and i remember from my time with the Samsung vibrant that sometimes, even if nothing comes up on the screen, the device might be picked up by Odin after doing the dl mode button combo
Click to expand...
Click to collapse
I will try and post back here.
Thanks for sharing your thoughts though.
freelancer81 said:
I brought a friend's Note and charged using my usb charger/cable...it is working ok.
My Note is about 2 months old and is still under warranty period. As a last resort, I can send it to them.
As you have root and custom rom then warranty is void .
If Samsung cannot tell that you have root and custom rom is a different matter .
Click to expand...
Click to collapse
Have you tried plugging in to your pc, see if odin recognizes it? If so try flashing stock samsung rom.
Sent from my GT-N8013 using XDA Premium App
rail205 said:
Have you tried plugging in to your pc, see if odin recognizes it? If so try flashing stock samsung rom.
Click to expand...
Click to collapse
I tried it....not detected...
It's very strange...no backlit or sound even when pressing power, power+vol up/vol down combos.
There was no error at all while flashing the ARHD 9.0.....and when I click on the finish and restart/reboot button at the end, boom..it shutdowns and dies on me...
I have googled it but no one has ever come across this kind of problem.
Since it is completely dead, there is a chance that sammy will not know it's rooted and running custom firmware.
Thanks to you and JJEgan for your concerns and suggestions.
As it sounds like a hardware issue, Samsung will likely fix it under warranty. At least that was my experience with Asus on my previous tablet.
Sent from my Vivid 4G using xda app-developers app
Do you know.if your battery was almost dead when flashing that last. Rom? I've heard that can brick ur device if it dies in flashing process. (Even tho you said flash completed) but who knows?
trevor7428 said:
Do you know.if your battery was almost dead when flashing that last. Rom? I've heard that can brick ur device if it dies in flashing process. (Even tho you said flash completed) but who knows?
Click to expand...
Click to collapse
I am not very sure about the exact battery percentage but yeah, it was low...somewhere about 10%~30%.
So, does that mean there is no way to revive it?
:crying:
freelancer81 said:
I am not very sure about the exact battery percentage but yeah, it was low...somewhere about 10%~30%.
So, does that mean there is no way to revive it?
:crying:
Click to expand...
Click to collapse
Unfortunately not without a new motherboard it seems like. If the is no sign of life, no recovery, no download mode and can't flash via oden or kies on computer with proper drivers installed. Then it sounds like a hard brick. Not recoverable unless new motherboard or JTAG. :/
Sorry man. But in future never flash if less than 30% battory. I've heard some pple say not below 50%
I don't know if your 10.1 died while flashing, but if so it could hard brick
50% is the suggested level of battery because flashing actually uses a large amount of battery. Also the tablets seem to power down things at 10%power.
Could be it shut off if the power dropped below 10%. This is why we suggest to not flash below 50%...
trevor7428 said:
Unfortunately not without a new motherboard it seems like. If the is no sign of life, no recovery, no download mode and can't flash via oden or kies on computer with proper drivers installed. Then it sounds like a hard brick. Not recoverable unless new motherboard or JTAG. :/
Sorry man. But in future never flash if less than 30% battory. I've heard some pple say not below 50%
I don't know if your 10.1 died while flashing, but if so it could hard brick
Click to expand...
Click to collapse
ultramag69 said:
50% is the suggested level of battery because flashing actually uses a large amount of battery. Also the tablets seem to power down things at 10%power.
Could be it shut off if the power dropped below 10%. This is why we suggest to not flash below 50%...
Click to expand...
Click to collapse
so sad....lesson learnt too late....the hard way :crying:
But I guess I have learnt one more way of hardbricking a device.
dude, seems like maybe a problem with your "main board"... i had the same issue at my galaxy tab 2, and i sent it to the shop ( because its passed warranty period already)...
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