Stuck in Splash screen - Android Q&A, Help & Troubleshooting

I have a Coolpad 3300a that's stuck in the splash screen. I've tried a soft & hard reboot (3x). Plugged into comp and it's "recognizes" an Android device, but does not display anything on/from the phone itself. Must remove battery to shut phone off. Have done a "search" pertaining to this problem, but have not been able to obtain a "fix". There are others with the same problem (on the "net" search), so I'm hoping someone here will have an answer for me.
Appreciated:
Rick

69Rixter said:
I have a Coolpad 3300a that's stuck in the splash screen. I've tried a soft & hard reboot (3x). Plugged into comp and it's "recognizes" an Android device, but does not display anything on/from the phone itself. Must remove battery to shut phone off. Have done a "search" pertaining to this problem, but have not been able to obtain a "fix". There are others with the same problem (on the "net" search), so I'm hoping someone here will have an answer for me.
Appreciated:
Rick
Click to expand...
Click to collapse
What were you doing or what did you do before the issue?
Can you get to recovery? Even being on stock recovery can help.

ninjasinabag said:
What were you doing or what did you do before the issue?
Can you get to recovery? Even being on stock recovery can help.
Click to expand...
Click to collapse
Re: ninjainabag
Thank You for responding and my apologies for not getting back to you sooner!. I'll answer in the order of your questions.
#1. Charging the phone via the comp/USB port. #2. Yes, and have been there. However the "recovery" menu on this phone only goes as far as "wiping cache", "wipe data/factory reset", "update from SD card" and "reboot now". Wiping cache and factory reset (3x) accomplished nothing! #3. Agreed, but never installed one (secondary stock recovery). 2 questions now... could I possibly D/l and install an O.S. from the SD card?, and/or use a "recovery" program from the computer through the phone?
Appreciate your response"
Rick

You're fine homey.
Your phones not, but you are. The Coolpad avail is the budget device for people who can't afford a budget device. So there's not much in the way of documentation for the 3300a.
In my personal opinion on the subject, you'd seriously just be better off picking up a new one.
-no recovery.
-no stock firmware available
-no support on the web (xda, AF, 4PD)
What service provider are you using? If you're looking to replace the phone. I can give a couple of suggestions that would help you make sure this doesn't happen again.

Related

[Q] Stuck in Boot screen!

Im going to lose my mind! I've searched and read and found no real answer..... Is there anyway that I can get my phone out of the boot screen?
Ive downloaded and rooted before and never had a prblm! I download this certain Rom Lastnight and all of a sudden my phone is stuck on the boot screen! I've tried everything i can with it and no luck. Does anyone have some type of info on what i can do or is there no hope for my poor lil droid?
Please let me know!
Thanx in advance!
Have you tried a battery pull? Pop that out and back in, reboot into recovery and restore your nandroid back up. Should be fine from there...
What I do when this happens to me is pull the battery, wipe my phone, re-apply the rom, then reboot.
-If that does not work, then revert back to your nand backup.
Thanks for the ideas but I tried both of those actions first and got nothing in return. This sukks! I even tried to go back and load the PB00img zip tha i had and no go. I'm guessing that i Bricked this dam Phone!
Back to the Blackberry! Damn!
Do you think its possible that i can load a new Rom and try to boot the phone into recovery and flash that zip? The problem seems to be my boot screen! I've seen post with people with similar "situations" <--------lol (not From Jersey shore) and tried those methods and once again nothing.
Sucks that you are still having this issue. The next step I can think of would be if you have SDK set up then once it is stuck on the boot screen, run a logcat and post it here so someone that is smarter than I can figure out where you are running into problems at. You'll need to navigate to your SDK/tools folder (in the Command window of course...) and then once there just type in: adb logcat .
This will result in a myriad of crazy computer language stuff. Should be able to tell us something at least.
First, take a deep breath; your phone is not bricked. Far from it in fact.
Second, prove to yourself that it isn't bricked by booting it into the custom recovery:
Power it off, and then hold down Vol-Up (first) and the End (second); keep pressing both buttons until the three skating droids have appeared. The custom recovery menu should pop up about 10-12 seconds after that.
Third, download "some other certain ROM" (I get to be as vague as you are, right?) to your PC, and get it to the root folder of your SD card somehow. Look up "USB-MS toggle Amon_RA" if you don't already know what that is.
Fourth, flash that "some other certain ROM" and prove to yourself that your phone is not bricked, making sure that you perform a "Wipe data/factory reset" first before you flash the ROM.
Then, after you've shown yourself how it is possible to do these steps, go back and try to figure out why the other "certain ROM" doesn't work on it's first boot. Try popping out the SD card before you boot it to see if that is the trouble.
bftb0
@es0tericcha0s, Thanks for the response but instead of doing more harm to the phone i just took it to VZW, (Kinda) Explained what happen and they switched it out no prob.
@bftb0 lol Be as Vague as possible.... I didn't want to say any particular Rom for the simple fact that who ever did the Rom i'm sure worked hard at it, And evevn tho i'm not new at this, it could very possibly be my mistake somewhere in installing it! SO I choose to respect the XDA and The Dev But thanks for your awesome response! (no Sarcasm intended) lol

Optimus V, cannot force into recovery mode

Before I get flamed or eaten up by people who I have so inconvenienced their day by creating a question that has been asked before, I have searched for this.
On the site, and on Google itself for a solution to my problem. So please bare with me and help me out, if you can.
I own an Optimus V. The phone is rooted, but it has no custom ROM installed onto it at all. I had the CM ROM manager, but that was it.
I wanted to factory reset my phone because I was having texting issues, so first thought to mind, lemme just go ahead and reset it. #stupid
Now, the LG logo flashes, fades away and then I am stuck at a black screen (the LCD is still on) and it doesn't go away. I have tried holding home button + volume down + lock button, and home button + volume up + lock button, and even when I press the camera button it occasionally turns on and off. All of the threads here about this issue are all from phones that had custom ROMs flashed onto them, and are all about getting the recovery onto the SD card and installing your ROM off the card.
I don't want that. I just want my phone to turn on again after its reset...
Please help
Also, some information I may have been missing:
The phone is rooted with Gingerbreak 1.2.
If this means anything, I received a replacement phone after September first due to a past issue, so I'm not sure if it has the newer screen or not. Also, I might have put recovery from Clockwork Mod. I'm not sure though, but as stated before, I have not installed any custom ROMs on to this phone.
I factory reset this phone a few months ago while rooted with the same options (although I didn't have the CM ROM manager...).
In other words, as far as I know, I probably did put recovery from Clockwork Mod. I really don't want to go out and buy a new phone
If your phone is just rooted and you do a factory reset it shouldn't hurt the phone at all, If your phone is rooted and have clock work mod installed and did a factory reset it shouldn't hurt the phone at all, when you do a factory reset to a phone all it is doing is erasing info, apps, contacts etc...its not deleting or restoring system files. Now you say that you did a factory reset and now there's a black screen and you can not go into clock work mod (cwm)? did you have cwm flashed from rom manager? I do not understand what you mean "I had the CM ROM manager, but that was it" Do you mean you had clock work mod or just rom manger? Sounds to me like you didn't have clock work mod on your phone at all, when you root your phone flash clock work mod, it can save alot of headaches, if you had cwm you could of just flashed a new custom rom. If you have a warranty for that phone just take it back and tell them it doesn't work and your having problems. I have taken my phone back a couple times at radio shack and it was soft brick and they didn't even notice. Sounds to me like its just a faulty phone that you bought (its normal it happens) nothing that you did at all, hope this helps
ErkelMan said:
I wanted to factory reset my phone because I was having texting issues, so first thought to mind, lemme just go ahead and reset it.
Click to expand...
Click to collapse
First of all: How did you "factory reset" your phone? And sorry to ask, but how can it be that you do not know if you have custom recovery or not? As far as I know the only way to factory reset the phone is to enter the custom recovery and choose the corresponding option, or to start the stock LG recovery which would do this automatically. So how can you not know after having reset which recovery did it?
Anyway, since you are stuck now, there seems no other possibility than unbricking your phone using kdz (please search in the sticky section) or getting it to service.
I assume he ment Factory reset from the options in the phone...settings/privacy/factory reset
Sent from my HTC Wildfire S using xda premium
Android311 said:
I assume he ment Factory reset from the options in the phone...settings/privacy/factory reset
Click to expand...
Click to collapse
O.k. ... in my (german) P500 this option - which I was not aware of until now - would have to be translated to "reset memory/storage", but not "factory reset" which I only knew from custom recovery. Anyway, in my opinion this should not be capable of bricking a device, because all it should do is delete the /data partition.
And even more it should under no circumstances be capable of corrupting the recovery partition... therefore I can only repeat my previous suggestions (assuming that accessing recovery is not working):
1) Try unbricking using kdz; or
2) Go to LG service.
Considering the description of the thread starter I would believe that the hardware is defective.
One other thing to the thread starter: What do you mean by "lock" button? The power button? The combo for accessing recovery is holding home+vol- and then pressing power until recovery starts. And what do you mean by "camera" button??? There is no such button on my P500 at least... And what does it mean when you say the device starts when pressing this "camera" button?
Mine says factory data reset, that's what I'm trying to understand why and how it bricked
Sent from my NookColor using xda premium

Tf201 Help me please.

Hi,
I recently unlocked and rooted my device. Asus Transformer Prime (TF201).
I tried to boot it into recovery, wouldn't boot the rom, kept freezing, hard reset it. Then it booted into the official android version, I was running 4.1.1, build # 10.4.2.18
Then I went into recovery, and I was like "oh yeah, I remember reading that it has to be a fresh install, that way there's no incompatibility". So I decided to press the down button until I got to erase everything in the menu, I did it. Erased it, device reset itself, and now it's stuck in the main loading screen, where it says Asus, this device is unlocked in the top left, and the nvidia symbol in the bottom right. The device wont boot into anything, not even recovery settings. Is there a fix? Or did I just make my tablet a paper weight?
I tried searching the web, I found all these articles, and frankly I'm very overwhelmed, and didn't know what to do or which one to read. I just got the tablet as a Valentines Day gift from my wife, and I would have to have ruined it. Please help me.
EDIT: I got my device to appear as "APX" in devices and printers, it's an unknown device. But I'm still lost.
Hi
Thanks for writing to us at XDA Assist. Please standby while we have your thread/question moved to the appropriate sub-forum for your device.
For future reference you can find your device sub-forum here (bookmark/subscribe this):
Asus Eee Pad Transformer Prime
Within that section you will find a dedicated q&a sub-forum (this is where your thread is going to be moved to):
Eee Pad Transformer Prime Q&A, Help & Troubleshooting
Good luck!
Bump, could really use some help...
GiordyWarner said:
Bump, could really use some help...
Click to expand...
Click to collapse
There is only hope, if you can manage to get into bootloader screen by pressing power + vol down.
APX mode would only help you, if you had pulled your nvflash files.
GiordyWarner said:
Hi,
I recently unlocked and rooted my device. Asus Transformer Prime (TF201).
I tried to boot it into recovery, wouldn't boot the rom, kept freezing, hard reset it. Then it booted into the official android version, I was running 4.1.1, build # 10.4.2.18
Then I went into recovery, and I was like "oh yeah, I remember reading that it has to be a fresh install, that way there's no incompatibility". So I decided to press the down button until I got to erase everything in the menu, I did it. Erased it, device reset itself, and now it's stuck in the main loading screen, where it says Asus, this device is unlocked in the top left, and the nvidia symbol in the bottom right. The device wont boot into anything, not even recovery settings. Is there a fix? Or did I just make my tablet a paper weight?
I tried searching the web, I found all these articles, and frankly I'm very overwhelmed, and didn't know what to do or which one to read. I just got the tablet as a Valentines Day gift from my wife, and I would have to have ruined it. Please help me.
EDIT: I got my device to appear as "APX" in devices and printers, it's an unknown device. But I'm still lost.
Click to expand...
Click to collapse
Hi, u can follow the steps listed in this blog. I just installed CM11 using the same steps over the weekend. U need to perform a factory reset and wipe the cache after u installed the ROM using the CWM recovery. If not, it will be struck in the boot screen with the arrow going in circle. Below is the blog address:
d3-media.blogspot.sg/2014/08/upgrading-asus-prime-tf201-to-android.html
Good luck flashing!!
gsanglan said:
Hi, u can follow the steps listed in this blog. I just installed CM11 using the same steps over the weekend. U need to perform a factory reset and wipe the cache after u installed the ROM using the CWM recovery. If not, it will be struck in the boot screen with the arrow going in circle. Below is the blog address:
d3-media.blogspot.sg/2014/08/upgrading-asus-prime-tf201-to-android.html
Good luck flashing!!
Click to expand...
Click to collapse
This has nothing to do with what he is asking.
flumpster said:
This has nothing to do with what he is asking.
Click to expand...
Click to collapse
Hi,
I've same problem!
I tried to flash to android 5.0. I tried many things via twrp and now, thats it:
My TF201 stucks also at bootscreen and the recovery menu (Power on + Vol.Down) won't work. That means I'm not able to get in fastboot mode or something like that. The only possiblity to switch the device off at the moment is to unplug the battery
I've searched for a solution in many boards, but unitl now i haven't found anything.
At the moment it seems that the only possibility we have, is to change mainboard, or to try to connect via an external programmer (for flashing the memory), but that would be for sure not the easiest way, or it could be also nearly impossible.
So at the moment I'm praying to god, that someone will have another solution and will post it here, because otherwise I can cast away my loved transformer prime :crying:
Looking forward to hear any news about that topic :fingers-crossed:
Jimboy00 said:
Hi,
I've same problem!
I tried to flash to android 5.0. I tried many things via twrp and now, thats it:
My TF201 stucks also at bootscreen and the recovery menu (Power on + Vol.Down) won't work. That means I'm not able to get in fastboot mode or something like that. The only possiblity to switch the device off at the moment is to unplug the battery
I've searched for a solution in many boards, but unitl now i haven't found anything.
At the moment it seems that the only possibility we have, is to change mainboard, or to try to connect via an external programmer (for flashing the memory), but that would be for sure not the easiest way, or it could be also nearly impossible.
So at the moment I'm praying to god, that someone will have another solution and will post it here, because otherwise I can cast away my loved transformer prime :crying:
Looking forward to hear any news about that topic :fingers-crossed:
Click to expand...
Click to collapse
You say this "My TF201 stucks also at bootscreen and the recovery menu". Does that mean you can still access recovery (TWRP)?
flumpster said:
You say this "My TF201 stucks also at bootscreen and the recovery menu". Does that mean you can still access recovery (TWRP)?
Click to expand...
Click to collapse
No, thats the problem, since yesterday it is not possible, because I tried to flash back to an older version of TWRP, and since that I can't access RCK and then I tried to wipe data, and since that, I even can't access to recovery console (Power on + Vol.Down).
That means I can't do anything at the moment, I see only the asus boot logo and that's it.
So I have no idea to communicate with the tablet at the moment.
The problem was, that I was not really careful, because my opinion was, that it's impossible to brick the whole tablet, but now it's gone!
Is that the end of the story, or do you know therefore a solution?
Regards,
Jim
Seems that you are in APX mode. Hope you have your blob + nvflash and wheelie to restore the bricksafe.img. (It saved my TF when i was in your position)
Good luck
Jimboy00 said:
No, thats the problem, since yesterday it is not possible, because I tried to flash back to an older version of TWRP, and since that I can't access RCK and then I tried to wipe data, and since that, I even can't access to recovery console (Power on + Vol.Down).
That means I can't do anything at the moment, I see only the asus boot logo and that's it.
So I have no idea to communicate with the tablet at the moment.
The problem was, that I was not really careful, because my opinion was, that it's impossible to brick the whole tablet, but now it's gone!
Is that the end of the story, or do you know therefore a solution?
Regards,
Jim
Click to expand...
Click to collapse
Unfortunately unless you have nvflash backups then you will have to get the board replaced. Forget contacting Asus as they would charge you more than the tablet is worth. Try and find one with a smashed screen on ebay etc cheap that still works that you can swap the board out from.
lemicp said:
Seems that you are in APX mode. Hope you have your blob + nvflash and wheelie to restore the bricksafe.img. (It saved my TF when i was in your position)
Good luck
Click to expand...
Click to collapse
Thanks for your feedback,
So I don't have these files :crying:
I found also another thread with same story, and it seems that I can search for a new MoBo....
http://forum.xda-developers.com/showthread.php?t=2143942
...or buy a new tablet, maybe the better solution...

[Q] Encryption Unsuccesful! Urgent help required!

I've been running Blisspop 5.1.1 on SGS3 with TWRP as my recoverey. Lately, I've been having many issues with my battery. Yesterday evening, I suddenly got the message of encryption unsuccesful on my phone. I tried every possible thing to do get rid of that message, but the phone wouldn't budge. My only option was to hit the phone resest button and see what happens, I understand running a custom rom with root excess can inexplicably damage my phone in such situations after reading a lot of posts.
The phone now displays the S3 logo and keeps flashing at the teamwin recovery splash and blinks right there.
I need urgent help to retrieve it back and any leads on this will be greatly appreciated.
Thank you!
you need a usb/otg cable..
shreenit said:
I've been running Blisspop 5.1.1 on SGS3 with TWRP as my recoverey. Lately, I've been having many issues with my battery. Yesterday evening, I suddenly got the message of encryption unsuccesful on my phone. I tried every possible thing to do get rid of that message, but the phone wouldn't budge. My only option was to hit the phone resest button and see what happens, I understand running a custom rom with root excess can inexplicably damage my phone in such situations after reading a lot of posts.
The phone now displays the S3 logo and keeps flashing at the teamwin recovery splash and blinks right there.
I need urgent help to retrieve it back and any leads on this will be greatly appreciated.
Thank you!
Click to expand...
Click to collapse
Don t reset your phone go back to twrp and do a factory reset..after that do a format data type in yes..dont reboot ...put a custom rom to your usb/otg drive thats specific for your phone.. Then flash it this is just to get you going...
paztine said:
Don t reset your phone go back to twrp and do a factory reset..after that do a format data type in yes..dont reboot ...put a custom rom to your usb/otg drive thats specific for your phone.. Then flash it this is just to get you going...
Click to expand...
Click to collapse
I did have to reset. There was no other option. It is now stuck on the page of team recovery and constantly flashes. Is there a way out for this?

Phone keeps vibrating/showing Mi Logo when "off"

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

Categories

Resources