Hello,
I am encountering a strange problem with my new Redmi Note 2, purchased from Top One. Whenever it is off and the battery is in, every 30 seconds it will vibrate and momentarily flash the white Mi logo as if it is about to turn on, then it will go back to black, then do this again in ~30sec. I have tried removing the back of the phone to see if it is an issue with the power button but it continues to happen whenever the battery is in. If battery is removed for ten seconds and then put back, the issue stops -- but then as soon as I turn the phone on, and then power off, it starts again. Otherwise the phone seems to run normally.
I flashed it to Miui 7.2.2.0 global stable Rom immediately after receiving it, and the problem has been there from the start. I believe I had noticed it there even before I flashed the new rom but I'm not sure as I hadn't yet interacted with the phone much...
Any suggestions? If you could please give me your instructions as basically as possible, and for Mac, I would appreciate it as I am a newbie. I flashed the rom using my Mac following instructions from the MIUI forms that showed how to do it in terminal after installing "adb/fastboot."
Thanks!
Seems to me that it is going into bootloader mode, instead of powering off completely. I am not sure how this could have started - perhaps a partially failed ROM upgrade at some point. I think you should return it (after restoring the original ROM) because trying to solve the problem might have to involve doing some low-level and extremely risky stuff.
Or for some weird reason the buttons get stuck and restarts to recovery.
When you try to boot into recovery, you get black screen->vibration->MI logo, and if you continue pressing the buttons you repeat the pattern.
Remove the battery cover and check if there's something in the buttons for a start..
Thanks for your responses
DarthJabba9 said:
Seems to me that it is going into bootloader mode, instead of powering off completely. I am not sure how this could have started - perhaps a partially failed ROM upgrade at some point. I think you should return it (after restoring the original ROM) because trying to solve the problem might have to involve doing some low-level and extremely risky stuff.
Click to expand...
Click to collapse
Could you give me a sense of what the low-level/risky stuff would be? Is it something I might be able to get done at a phone repair shop in the UK (where Xiaomi of course is not sold)? I ask because I'm required to pay for return shipping to China if I'm going to return device, and god knows how long the whole return process will take -- so if it's not a major hardware issue it might be worth it for me to explore finding a fix.
tonydeli7 said:
Or for some weird reason the buttons get stuck and restarts to recovery.
When you try to boot into recovery, you get black screen->vibration->MI logo, and if you continue pressing the buttons you repeat the pattern.
Remove the battery cover and check if there's something in the buttons for a start..
Click to expand...
Click to collapse
I don't see anything unusual in the buttons. As I said, if I remove the battery for ten seconds and then put it back in, I don't get this problem. It's only after doing a successful boot/shutdown (which works normally) that it starts again. So as far as I can tell it doesn't appear to be a mechanical problem.
littleozzyman said:
Thanks for your responses
Could you give me a sense of what the low-level/risky stuff would be? Is it something I might be able to get done at a phone repair shop in the UK (where Xiaomi of course is not sold)? I ask because I'm required to pay for return shipping to China if I'm going to return device, and god knows how long the whole return process will take -- so if it's not a major hardware issue it might be worth it for me to explore finding a fix.
Click to expand...
Click to collapse
The low-level+very risky stuff would involve flashing a full ROM. By "full", I mean inclusive of preloader, uboot/lk, etc. This is what makes it very risky, because if something goes wrong with the preloader/lk flash, the device could be bricked beyond what normal people could recover. An example of a ROM that flashes everything is: http://www.needrom.com/download/miui-7-2-3-0-redmi-note-2/
My current ROM is based on an earlier version of this, and I noted at the time it was released that it installs a preloader - but I am not sure whether I installed it complete with preloader or not (I probably did). From what I can see, nobody's device got bricked by installing this ROM, which is actually excellent (so much so that I inevitably return to it after trying something else). However, it is still risky to upgrade a preloader. I suspect that this may be what you need - but it may not resolve your problem anyway.
PS: beware of more recent Xiaomi ROMs that lock the bootloader. If you tried to do this risky process, you would be best advised to make sure that you are not flashing a ROM that locks the bootloader (i.e., the most recent ROMs coming out from Xiaomi).
DarthJabba9 said:
The low-level+very risky stuff would involve flashing a full ROM. By "full", I mean inclusive of preloader, uboot/lk, etc. This is what makes it very risky, because if something goes wrong with the preloader/lk flash, the device could be bricked beyond what normal people could recover. An example of a ROM that flashes everything is:
My current ROM is based on an earlier version of this, and I noted at the time it was released that it installs a preloader - but I am not sure whether I installed it complete with preloader or not (I probably did). From what I can see, nobody's device got bricked by installing this ROM, which is actually excellent (so much so that I inevitably return to it after trying something else). However, it is still risky to upgrade a preloader. I suspect that this may be what you need - but it may not resolve your problem anyway.
PS: beware of more recent Xiaomi ROMs that lock the bootloader. If you tried to do this risky process, you would be best advised to make sure that you are not flashing a ROM that locks the bootloader (i.e., the most recent ROMs coming out from Xiaomi).
Click to expand...
Click to collapse
Thanks for this. Could you point me to how I might be able to install a full official Xiaomi rom? (One that won't lock the boot loader.) My preference would be to get the global stable rom running as normal so that I can have the standard working phone with OTA updates. Or, is it easier to install this rom you've suggested with preloader, and then afterwards I can flash the official rom (assuming this fixes the problem)?
Also, are there any tutorials/clearer instructions for how to do this kind of install? The instructions on the link you've provided don't seem very clear...
Not sure if I'm gonna try this yet but leaning towards it if I feel confident enough I can execute it without screwing anything up...
littleozzyman said:
Thanks for this. Could you point me to how I might be able to install a full official Xiaomi rom? (One that won't lock the boot loader.) My preference would be to get the global stable rom running as normal so that I can have the standard working phone with OTA updates. Or, is it easier to install this rom you've suggested with preloader, and then afterwards I can flash the official rom (assuming this fixes the problem)?
Also, are there any tutorials/clearer instructions for how to do this kind of install? The instructions on the link you've provided don't seem very clear...
Not sure if I'm gonna try this yet but leaning towards it if I feel confident enough I can execute it without screwing anything up...
Click to expand...
Click to collapse
I personally wouldn't touch official ROMs with a bargepole. At the very least, xiaomi.eu, or ROMs based on it (like the one linked to). But each to his own. With regard to installation, I don't think you can get more detailed instructions than those given, which I will now try to present in clearer English:
Reboot to Recovery ( TWRP only )
Wipe Dalvik/Art
Wipe cache
Wipe data (note that TWRP allows you to do 2-4 in one go - they are the same as resetting to factory defaults)
Install ROM
Wipe cache and Dalvik/Art again (but do NOT wipe data)
Reboot
Wait for about 20 minutes while it builds Dalvik/Art, and other stuff
Done
Hopefully, this will cure the problem. If so, then you can install whatever ROM you want, following the same process as above. If not, then you still have an excellent ROM anyway.
By the way, doing any of this presupposes that you have already installed TWRP recovery. If not, then that is the first thing to do.
DarthJabba9 said:
I personally wouldn't touch official ROMs with a bargepole. At the very least, xiaomi.eu, or ROMs based on it (like the one linked to). But each to his own. With regard to installation, I don't think you can get more detailed instructions than those given, which I will now try to present in clearer English:
Reboot to Recovery ( TWRP only )
Wipe Dalvik/Art
Wipe cache
Wipe data (note that TWRP allows you to do 2-4 in one go - they are the same as resetting to factory defaults)
Install ROM
Wipe cache and Dalvik/Art again (but do NOT wipe data)
Reboot
Wait for about 20 minutes while it builds Dalvik/Art, and other stuff
Done
Hopefully, this will cure the problem. If so, then you can install whatever ROM you want, following the same process as above. If not, then you still have an excellent ROM anyway.
By the way, doing any of this presupposes that you have already installed TWRP recovery. If not, then that is the first thing to do.
Click to expand...
Click to collapse
Thanks for the English translation haha, I'll give this a shot. Just one more question -- when you write "install ROM", I should just treat the ROM the same way that I would any other, by flashing it via fastboot (as I did in OSX terminal) right?
littleozzyman said:
Thanks for the English translation haha, I'll give this a shot. Just one more question -- when you write "install ROM", I should just treat the ROM the same way that I would any other, by flashing it via fastboot (as I did in OSX terminal) right?
Click to expand...
Click to collapse
No. Steps 1 to 7 inclusive are done from TWRP Recovery.
DarthJabba9 said:
No. Steps 1 to 7 inclusive are done from TWRP Recovery.
Click to expand...
Click to collapse
Well, thanks again for your suggestion, but unfortunately it didn't succeed. I managed to install the custom full ROM you suggested with TWRP, and the problem persists; when the phone is off, I get this strange problem with the Mi logo flashing.
I'm investigating how to make a return, but I thought I would ask: do you have any idea whether this problem will negatively affect the phone in any other way? Because, if I'm unable to make a return, I think it's an issue I can live with (I rarely have my phone switched off anyhow), so long as it won't cause more problems down the line...
Something else I just realised: Apparently the problem doesn't occur when the phone is plugged into the USB (both electrical socket and computer). Starts up again as soon as I remove the plug. Perhaps that provides more context...
littleozzyman said:
Well, thanks again for your suggestion, but unfortunately it didn't succeed. I managed to install the custom full ROM you suggested with TWRP, and the problem persists; when the phone is off, I get this strange problem with the Mi logo flashing.
I'm investigating how to make a return, but I thought I would ask: do you have any idea whether this problem will negatively affect the phone in any other way? Because, if I'm unable to make a return, I think it's an issue I can live with (I rarely have my phone switched off anyhow), so long as it won't cause more problems down the line...
Click to expand...
Click to collapse
Well, I would hazard a guess that this is not a software problem. Clearly, the phone is trying to boot into bootloader mode or into recovery mode when it is meant to be completely switched off. This implies;
a) that there is a possibly a hardware problem somewhere (eg., something short-circuiting somewhere?), or
b) a virus/rootkit trying to dial home?, or
c) some other unknown fault?
None of these options would give me any peace of mind. If the problem is (b) then a good anti-virus or rootkit remover program would solve the problem. Search the PlayStore for those. If that doesn't solve the problem, then it's either (a) or (c) - and that is not good.
DarthJabba9 said:
Well, I would hazard a guess that this is not a software problem. Clearly, the phone is trying to boot into bootloader mode or into recovery mode when it is meant to be completely switched off. This implies;
a) that there is a possibly a hardware problem somewhere (eg., something short-circuiting somewhere?), or
b) a virus/rootkit trying to dial home?, or
c) some other unknown fault?
None of these options would give me any peace of mind. If the problem is (b) then a good anti-virus or rootkit remover program would solve the problem. Search the PlayStore for those. If that doesn't solve the problem, then it's either (a) or (c) - and that is not good.
Click to expand...
Click to collapse
Nothing shows up on anti-virus/rootkit. I guess I should really insist on getting a return. Hopefully they will process it without too much fuss/expense. If any other suggestions come to anybody in the meantime, I'd be glad to hear them.
I just noticed as well that someone posted with what seems to be the same issue to mine last year: http://forum.xda-developers.com/redmi-note-2/help/phone-rebooting-shutdown-t3232941 , with no resolution. Perhaps this is some kind of occasional manufacturing problem.
littleozzyman said:
Nothing shows up on anti-virus/rootkit. I guess I should really insist on getting a return.
Click to expand...
Click to collapse
Absolutely.
HW problem: Power Management IC
I too faced this problem and I suspected Battery to be the culprit . Anyway , i got it checked and repaired at a local (non xiaomi) repair shop that claims it was the issue with PMIC power management IC and that he has replaced the IC .
Now the phone works fine and does not enter into that bootloop even when charger is disconnected and phone is rebooted manually. I hope the problem is resolved .
However , the other issue is still persistent which is : copper colored washed out MI logo constantly appears on the screen and reinstallation of sw did not help either . In india these repairmen usually cant explain the problem area if it is outside of "Try and test" scheme .
I spent 1000INR to get it repaired but I highly doubt that PMIC is replaced. Coz this repair guy did this replacement in just 6 work hours. probability of getting the right part at right time at his disposal is very slim. And I had seen his workstation once, where i di not see any SMT repair station either. Which means that he cannot replace BGA package IC at all. Anyway, I will receive the phone tonight. Lets hope it works fine and the other problem gets rectified by flashing.
Saurabh Srivastava, Noida , India
Sorry for a very strange problem.... My wife still uses her old S III (I9300), although it is so outdated and partly broken. Some time ago we flashed CM 12, so that some apps who need a more up-to-date android can be used. But the phone is too slow, there is a crack in the display and sometimes it starts to reboot without any reason. There is not enough memory to install additional apps and without LTE it is no fun.
=> I want to buy a new smartphone for her, but she doesn't want to. She wants to save money and use it, until it is not usable any more.
Of course I could give it a good strike with a hammer or give it a treatment in the microwave oven, but I would prefer only a temporary lack of functions, so that perhaps later I can use it as backup phone for the kids. Therefore I am looking for some trick, app or system setting to SIMULATE, that the phone is broken. When she is happy with her new phone, I intend to "repair" it "by chance"....
Any ideas? How can I simulate, that the phone is broken? Thanks!
You need to hardbrick it.I dont know how to but you can Google it.
ArdaCsknn said:
You need to hardbrick it.I dont know how to but you can Google it.
Click to expand...
Click to collapse
Thanks for the reply! I googled, but i think i want to SOFTbrick it, not to hardbrick it. As I wrote above, I want to "revive" it after some time....
I think the simplest way may be to take the phone, create a backup of all data, put the phone into download mode, start flashing a stock ROM, remove the USB cable when it starts to flash the final file, and reboot the phone. Hopefully, the phone will display the "firmware upgrade encountered an error" message which can be resolved by re-flashing the stock ROM with Odin.
Based on my experience with flashing a stock ROM over a stock ROM, this procedure always leaves the data and apps intact.
cm_new said:
Thanks for the reply! I googled, but i think i want to SOFTbrick it, not to hardbrick it. As I wrote above, I want to "revive" it after some time....
Click to expand...
Click to collapse
Ah,sorry I read it but while replying I forgot somehow.Yeah, then you need to soft brick it .It can be achieved by deleting some system files.So phone can got into bootloop.If your wife doesnt now how to get in to recovery then you should be ok.
Stock rooted phone needed for this, activate factory app. It will give a black window with device information over everything onscreen. Disable factory app to remove it later on.
By flashing the stock firmware in an attempt to make it all better gives the perfect opportunity to pretend the process buggered it.
Put some clear tape on the battery contacts ?
Hello to whom may come upon this,
I flashed the v20-g8 engineer-laf file on my lg g8 att lg820UMi. I cannot personally boot back into my phone, nor even go into factory hard reset. When I boot into factory hard reset mode it does carry me to the finalized, "Do you wanna really reset all personal data etc...". But it just freezes after I press yes, and does not do nothing. I was trying to bootloader unlock my phone, but it was the wrong file or wrong format. It freezes in DL mode initially booting into DL mode and I can't access fastboot. Check s/n and imei does and factory reset yes, but continuing to actually factory reset and pressing the final yes; it hangs. So I do not know what to do. Rather there is an hardware fix to this internally or to just throw this phone in the trash. the digitizer on the phone is cracked, but the oled panel is still intact. Maybe someone could buy it for the microphone pieces and frame, but the motherboard on this phone is ****ed. I guess the boot.img is corrupted or whatever the bios to booting is dis-logged. Can anyone help? I wish it would just run the factory reset program fully then my system could restore itself, but we all know that the lg g8x att version does not have an kdz to be flashed plus the computer cant pick it up or communicate with the phone because it freezes in DL mode. Please help. I actually sort of love my phone(s). First time ever bricking an phone and usually an way out the hole but its like lg forced my in a ditch. Bad thing is I actually advertised this phone pretty well. LG cough...cough...do better or stop making phones for att because ATT is pretty stuck up because there towers and routers do the talk these days then their software. Ugh... Wasted my stimulus money
:crying::angel::crying::highfive:
Shryvone21 said:
Hello to whom may come upon this,
I flashed the v20-g8 engineer-laf file on my lg g8 att lg820UMi. I cannot personally boot back into my phone, nor even go into factory hard reset. When I boot into factory hard reset mode it does carry me to the finalized, "Do you wanna really reset all personal data etc...". But it just freezes after I press yes, and does not do nothing. I was trying to bootloader unlock my phone, but it was the wrong file or wrong format. It freezes in DL mode initially booting into DL mode and I can't access fastboot. Check s/n and imei does and factory reset yes, but continuing to actually factory reset and pressing the final yes; it hangs. So I do not know what to do. Rather there is an hardware fix to this internally or to just throw this phone in the trash. the digitizer on the phone is cracked, but the oled panel is still intact. Maybe someone could buy it for the microphone pieces and frame, but the motherboard on this phone is ****ed. I guess the boot.img is corrupted or whatever the bios to booting is dis-logged. Can anyone help? I wish it would just run the factory reset program fully then my system could restore itself, but we all know that the lg g8x att version does not have an kdz to be flashed plus the computer cant pick it up or communicate with the phone because it freezes in DL mode. Please help. I actually sort of love my phone(s). First time ever bricking an phone and usually an way out the hole but its like lg forced my in a ditch. Bad thing is I actually advertised this phone pretty well. LG cough...cough...do better or stop making phones for att because ATT is pretty stuck up because there towers and routers do the talk these days then their software. Ugh... Wasted my stimulus money
:crying::angel::crying::highfive:
Click to expand...
Click to collapse
bro enter edl and restore your stock file,i mean restore the stock file of which you loaded (backup fiile)
[email protected] said:
bro enter edl and restore your stock file,i mean restore the stock file of which you loaded (backup fiile)
Click to expand...
Click to collapse
I can't enter into dl mode at all...my phone is fuccked....
Did you come to any kind of solution? im in a very similar situation.
Hello everyone,
I hope everyone is keeping safe during these unprecedented times of Covid-19 (In India, things don't seem to be as good for now. Shall get better soon, hopefully!)
My A50S SM-A507FN is frequently getting restarted automatically since a week now. I have tried the basic steps like clear cache, factory reset etc. both from the phone settings as well as via hard reset menu, to no avail. It may be due to firmware or could be due to hardware issue (power IC maybe). I have seen a lot of A50S owners reporting same issue on Google, etc. but no concrete solution. People have mentioned that upon taking their phones to Samsung Service Center they are suggesting it being due to motherboard issue, and suggesting to change the motherboard @ INR 8000 which is insane IMO. I am thinking to flash the custom rom on the phone, as it may probably overrule the firmware or the laggy OS lag due to which this problem is occurring. Also, if the problem persist after flashing the rom, it will give me clarity that the issue may exist in the power IC indeed, and is not due to software. The only confusion though is, whether it's safe to flash the custom rom, considering the issue of sudden restart. I wonder if the phone will malfunction and restart in recovery mode too, for its not being operated via OS during that time. What if the process gets interrupted due to phone restarting during rom being flashed. It should not brick the device, right? At max I will have to boot the phone in TWRP mode again to flash the custom rom file, right? I used to flash custom roms a lot almost like a decade ago when I used to own HTC smartphones, but its been a while since I do this, and hence the doubts.
Please share your inputs, I will highly appreciate the same.
Thanks in advance!
vicky_crispy said:
Hello everyone,
I hope everyone is keeping safe during these unprecedented times of Covid-19 (In India, things don't seem to be as good for now. Shall get better soon, hopefully!)
My A50S SM-A507FN is frequently getting restarted automatically since a week now. I have tried the basic steps like clear cache, factory reset etc. both from the phone settings as well as via hard reset menu, to no avail. It may be due to firmware or could be due to hardware issue (power IC maybe). I have seen a lot of A50S owners reporting same issue on Google, etc. but no concrete solution. People have mentioned that upon taking their phones to Samsung Service Center they are suggesting it being due to motherboard issue, and suggesting to change the motherboard @ INR 8000 which is insane IMO. I am thinking to flash the custom rom on the phone, as it may probably overrule the firmware or the laggy OS lag due to which this problem is occurring. Also, if the problem persist after flashing the rom, it will give me clarity that the issue may exist in the power IC indeed, and is not due to software. The only confusion though is, whether it's safe to flash the custom rom, considering the issue of sudden restart. I wonder if the phone will malfunction and restart in recovery mode too, for its not being operated via OS during that time. What if the process gets interrupted due to phone restarting during rom being flashed. It should not brick the device, right? At max I will have to boot the phone in TWRP mode again to flash the custom rom file, right? I used to flash custom roms a lot almost like a decade ago when I used to own HTC smartphones, but its been a while since I do this, and hence the doubts.
Please share your inputs, I will highly appreciate the same.
Thanks in advance!
Click to expand...
Click to collapse
hi i am also facing same issue and i have same thoughts as you man, were you able to rectify/fix it
vicky_crispy said:
Hello everyone,
I hope everyone is keeping safe during these unprecedented times of Covid-19 (In India, things don't seem to be as good for now. Shall get better soon, hopefully!)
My A50S SM-A507FN is frequently getting restarted automatically since a week now. I have tried the basic steps like clear cache, factory reset etc. both from the phone settings as well as via hard reset menu, to no avail. It may be due to firmware or could be due to hardware issue (power IC maybe). I have seen a lot of A50S owners reporting same issue on Google, etc. but no concrete solution. People have mentioned that upon taking their phones to Samsung Service Center they are suggesting it being due to motherboard issue, and suggesting to change the motherboard @ INR 8000 which is insane IMO. I am thinking to flash the custom rom on the phone, as it may probably overrule the firmware or the laggy OS lag due to which this problem is occurring. Also, if the problem persist after flashing the rom, it will give me clarity that the issue may exist in the power IC indeed, and is not due to software. The only confusion though is, whether it's safe to flash the custom rom, considering the issue of sudden restart. I wonder if the phone will malfunction and restart in recovery mode too, for its not being operated via OS during that time. What if the process gets interrupted due to phone restarting during rom being flashed. It should not brick the device, right? At max I will have to boot the phone in TWRP mode again to flash the custom rom file, right? I used to flash custom roms a lot almost like a decade ago when I used to own HTC smartphones, but its been a while since I do this, and hence the doubts.
Please share your inputs, I will highly appreciate the same.
Thanks in advance!
Click to expand...
Click to collapse
Hi. Did you get any solution for A50S restart issue? I am facing the same. Did you try custom ROM or changing Power IC?