Related
Ok, so I have a serious problem... My phone is locked and when I touch the text bar to enter the password, no keyboard comes up. Important information:
- I just upgraded to jelly bean (the official one that came out today)
- as far as I can tell, everything is working fine, i just can't unlock it
- when I touch the text bar, it makes a noise, but no keyboard comes up
- was working fine immediately after the upgrade
- I got done fixing some settings and locked the screen
- this may have something to do with changing the default keyboard to Google Keyboard (it was acting a little funny immidiately after, like it was crashing)
- I have Android Lost installed, the unlock function isn't working, but others do work
- phone is encrypted
Unless someone has some ideas for me within the next couple hours, I'm going to wipe the phone. Obviously, I would prefer to not do that.
==========================
EDIT:
I've managed to use Android Lost to make some backups of some stuff, but I'm still trying to figure out how to unlock the screen. I've found that I'm able to install apps remotely from google play if that gives gives anyone some ideas.
=============================
EDIT2:
I had another idea. If this is a problem with the keyboard, is there a way for me to change it remotely? Can I install another one via the store?
Alright... I gave up on trying to get passed the lock screen and tried doing a factory reset. I was afraid of the super brick issue, so instead of doing a wipe in recovery mode, I used Kies to reflash it. However, that did nothing. The phone started back up and acted like nothing happened. It asked me for the same password, then got to the lock screen and had the same keyboard issue.
I've tried various roms, but nothing seems to wipe the encrypted information properly. At some point, I got it to forget the password, but it still thinks that one exists. I even rooted it and tried shostock3, but when it boots, it asks for a password. The old password doesn't work, so I can't get passed it. I tried entering the "wrong" password many times and it said it would wipe the phone, but it just restarted to the SAMSUNG boot screen and just sat there. I pulled the battery after half an hour...
I should note that stock gingerbread seems to work fine...
Does anyone have any ideas on how to wipe the encrypted data?
If you can push apps to it, try pushing an app like no lock or something.
Short answer: No.
It is probable that encryption information is stored in the efs (encrypted file system) folder. That's where the imei and other critical stuff is stored. I don't believe anyone who posts here in the I777 forum really has a grasp on how phone encryption works though. I've only seen one other person post here who had an issue with an encrypted phone, and he was unable to solve his problem as far as I know.
If you have a proper backup of the efs partition from before the phone was encrypted, it is possible that you could solve the problem by restoring that partition. But I'm not even sure you could write to that section of the phone memory with adb with the phone in it's current state. Edit: if you can boot into stock gingerbread normally, then you can restore an efs backup, if you have one.
I'm guessing you could send it to Samsung and they could fix it for you probably.
I finally got it working. I'm not sure what combination of things did it, but I had to restore it to stock jelly bean (via kies) to get it to wipe the encryption. I guess the stock rom knows how to properly wipe it when you keep entering the wrong password. After I got it all cleaned up, I put shostock3 back on. When the battery charges back up, I'm going to try encrypting it again (in shostock).
However, now I found another issue (may or may not be a real problem). I wanted to check if the phone was still unlocked, so I dialed *#SIMLOCK# and it says "Connection problem or invalid MMI code."
Tada!
Creepy, my good friend, would be referring to me and as you know SCIU I didn't ever get it to unlock the phone. Oddly enough a stock ICS rom (my mom now has my phone right up the road so I may try this to see if it will work and then go back to ShoStock3) works fine. I have nothing hidden from the phone storage, everything shows up, it is actually unlocked and rooted though not a custom bios err firmware/ROM because when that is put on there the encryption issues come back and the password is asked for. If the correct password is entered (and my KEYBOARD comes up but I didn't change it from the Android/Samsung one) it proceeds to enter whatever it is supposed to (my guess is the POST area like on a computer when it is entering Windows/Linux, etc.) but the screen stays black (ShoStock logo doesn't even appear if I remember correctly or it does show then goes to black loading screen with the Samsung logo and that is it, perm stuck). However I did try flashing back to Gingerbread ROMs and ICS ROMs though not through official KIES.
SCIU I may have to give this a try if my mom don't mind it and see if that helps fix the problem. Thanks for starting this thread. I am sorry I didn't respond to the PM you sent me (my LGOG, Triple OG, OG, TRIPLE OG, Optimus G AT&T Phone has screen cracked twice and is unresponsive on two different phones so I sent that in to warranty repair [rapid heating and cooling issues]) and haven't been on XDA for a week. If there is anything else you need to ask or bounce ideas off of me then I am all for it.
As far as encryption goes, the process works the same as any other encryption algorithms used (MD5/HASH/SHA-!, etc.) using a basic replica of most file systems although mobile storage tends to work a tad differently. Unfortunately, the freezer trick, brute force, nor any other cracking methods I was able to try at home worked to get it to open up. I tried getting into the EFS area of the phone but never could get to the directory or have it display.
Again thanks SCIU and as I stated I may give this a try if my mom don't care.
Eagle
i've the same problem here but i cann't use kies when my phone is locked .... so what can i do??
rawan-omer said:
i've the same problem here but i cann't use kies when my phone is locked .... so what can i do??
Click to expand...
Click to collapse
You can get the full stock jelly bean Odin flashable tar in the Download Repository. See link in my signature. According to sciguy125, flashing stock jb and then inputting repeatedly the wrong password will clear it. I'm not sure how many times it takes, 5 or 10 I think. I've never worked with an encrypted phone. I'm just repeating what I have read others say. I've seen the above posted by at least one other person. You should be able to flash the stock firmware using Odin. The one you want is I777UCMD8
my phone screen is locked (with word password) , Huawei, and the keyboard doesnt show up when i click the box? tried reseting it, cant go to settings whatsoever! i didnt damage my phone in any way either. need help asap!!
moselyy said:
my phone screen is locked (with word password) , Huawei, and the keyboard doesnt show up when i click the box? tried reseting it, cant go to settings whatsoever! i didnt damage my phone in any way either. need help asap!!
Click to expand...
Click to collapse
Friend, this is the forum for the S2 (Samsung), so you won't find anything about Huawei devices here - best to ask your question in the forum for your device.
That being said if you are rooted and have a custom recovery, simply power the device off and boot into recovery and perform a factory reset from there. If that doesn't work do a full wipe (this means wiping /system), then re-flash the ROM/gapps.
me too!!! do you have some tips for me?? i almost fainted when i knew that the keyboard isnt working.... i do have a lot of important files in my phone.
Easy, you fools! JUST KIDDING lol Connect an external keyboard. Restart the phone with the keyboard plugged in and you'll have one chance to input the pass every time you restart. Good luck, bosses!
my phone screen is locked (with word password) , SAMSUNG GALAXY TAB 3V, and the keyboard doesnt show up when i click the box? tried reseting it, cant go to settings whatsoever! i didnt damage my phone in any way either. need help asap!
My sumsang keyboard has stopped I cannot do nothing because is secure by password can you help please
I got the same problem but everything on my phone is fine except it doesn't let me enter the password I dnt wanna factory reset it cause I got important pictures in it any suggestions on how to get my keyboard working.
Solution that worked for me
Hello all,
I usually don't post things around, but something told me to do this, since I don't see any threads talking about this solution.
My solution was the following:
Went to google play store on my computer via chrome. Logged in to the user attached to my play store and re-installed all keyboard apps I have.
That worked beautifully and hope this helps other people!!
I have a sumsung ace 3 gts7272 that has been infected with a virus called com.system.patch. here's what it does:
1- the first thing I noticed was that a white page pops up for like a second and it says com.system.patch
2- the second thing is very hard to not notice. a white noise page pops up every 10-30 seconds and the phone restarts and ANY CHANGES YOU DO BEFORE THE RESTART WILL BE GONE. YOU CAN'T CHANGE ANYTHING.
3- in settings>security>administrators you can see com.system.patch as administrator and android is not ticked, you can tick it but once the device restarts all is back to the way it was.
4- you cannot remove com.system.patch from app manager.
5- you cannot deactivate its authority as administrator.
6-you cannot factory reset it is deactivated. secret code does not work and using keys after it says factory reset done and it restarts everything is back to the way it was.
7- I removed the sd card and the background photos are still there.
8- I can connect it to the pc as storage device but nothing more than that.
9- I tried odin3.9 and it does the whole download process but after reset it goes back to the way it was and I can never get the PASS message.
10- I tried professionals who work for sumsung but after trying everything they just said you should change parts that would cost 3/4 of the phone's price which is not worth it.
I still don't wanna give up. Please help me get rid of this annoying virus.
maxapay said:
I have a sumsung ace 3 gts7272 that has been infected with a virus called com.system.patch. here's what it does:
1- the first thing I noticed was that a white page pops up for like a second and it says com.system.patch
2- the second thing is very hard to not notice. a white noise page pops up every 10-30 seconds and the phone restarts and ANY CHANGES YOU DO BEFORE THE RESTART WILL BE GONE. YOU CAN'T CHANGE ANYTHING.
3- in settings>security>administrators you can see com.system.patch as administrator and android is not ticked, you can tick it but once the device restarts all is back to the way it was.
4- you cannot remove com.system.patch from app manager.
5- you cannot deactivate its authority as administrator.
6-you cannot factory reset it is deactivated. secret code does not work and using keys after it says factory reset done and it restarts everything is back to the way it was.
7- I removed the sd card and the background photos are still there.
8- I can connect it to the pc as storage device but nothing more than that.
9- I tried odin3.9 and it does the whole download process but after reset it goes back to the way it was and I can never get the PASS message.
10- I tried professionals who work for sumsung but after trying everything they just said you should change parts that would cost 3/4 of the phone's price which is not worth it.
I still don't wanna give up. Please help me get rid of this annoying virus.
Click to expand...
Click to collapse
As we discussed earlier, "com.system.patch" is not a virus, but rather an extremely stubborn and annoying form of adware. In most case, it can be simply deleted whether it has administrator privileges or not from a root-enabled file manager (Root Explorer?) or from a custom recovery with file manipulation capabilities (TWRP?). Is your device currently functional and rooted and if so have you tried to locate and delete the apk from a file manager (not the "Application Manager" in settings) or even a terminal prompt?
There is a forum dedicated to Ace 3 Development at http://forum.xda-developers.com/ace-3/development where I see several recoveries and ROMs that might be of interest to you. Don't give up yet!
Mike B. said:
As we discussed earlier, "com.system.patch" is not a virus, but rather an extremely stubborn and annoying form of adware. In most case, it can be simply deleted whether it has administrator privileges or not from a root-enabled file manager (Root Explorer?) or from a custom recovery with file manipulation capabilities (TWRP?). Is your device currently functional and rooted and if so have you tried to locate and delete the apk from a file manager (not the "Application Manager" in settings) or even a terminal prompt?
There is a forum dedicated to Ace 3 Development at http://forum.xda-developers.com/ace-3/development where I see several recoveries and ROMs that might be of interest to you. Don't give up yet!
Click to expand...
Click to collapse
I can't install anything. It restarts too soon. I have no time to do anything. There must be another way.
maxapay said:
I can't install anything. It restarts too soon. I have no time to do anything. There must be another way.
Click to expand...
Click to collapse
Can you get into "Safe mode" (if applicable to your ROM) as suggested in the thread at http://forum.xda-developers.com/showthread.php?t=1090072? Do you have a custom recovery from which you could simply delete the apk or even reload a fresh copy of your ROM (or upgrade to a newer ROM)? The link I posted earlier seems to offer quite a few possibilities.
Mike B. said:
Can you get into "Safe mode" (if applicable to your ROM) as suggested in the thread at http://forum.xda-developers.com/showthread.php?t=1090072? Do you have a custom recovery from which you could simply delete the apk or even reload a fresh copy of your ROM (or upgrade to a newer ROM)? The link I posted earlier seems to offer quite a few possibilities.
Click to expand...
Click to collapse
I can go into safe mode, however, the same problem exists there as well. it doesn't give me enough time to do anything it keeps restarting.
maxapay said:
I can go into safe mode, however, the same problem exists there as well. it doesn't give me enough time to do anything it keeps restarting.
Click to expand...
Click to collapse
Then I guess a custom recovery or reflashing a ROM would be your best bet. Once again, good luck!
Mike B. said:
Then I guess a custom recovery or reflashing a ROM would be your best bet. Once again, good luck!
Click to expand...
Click to collapse
as I said in my post that did not work as well. It's like the phone is in freeze mode and everything goes back to the way it was.
maxapay said:
as I said in my post that did not work as well. It's like the phone is in freeze mode and everything goes back to the way it was.
Click to expand...
Click to collapse
It's not clear from your posts whether you have a custom recovery, whether you can access your recovery (custom or stock), or whether you have tried to reflash a ROM. You mention "Odin" but not what you tried to use it for nor whether you tried other methods for replacing your ROM or at least /system since Odin is far from perfect (and actually useless on many platforms/devices).
I'm somewhat familiar with your phone model and it's a good little unit worth fighting for. Please understand that the more exact you are in describing your problem, the more likely it is that someone will be able to help you. Trust me, we're on your side!
Mike B. said:
It's not clear from your posts whether you have a custom recovery, whether you can access your recovery (custom or stock), or whether you have tried to reflash a ROM. You mention "Odin" but not what you tried to use it for nor whether you tried other methods for replacing your ROM or at least /system since Odin is far from perfect (and actually useless on many platforms/devices).
I'm somewhat familiar with your phone model and it's a good little unit worth fighting for. Please understand that the more exact you are in describing your problem, the more likely it is that someone will be able to help you. Trust me, we're on your side!
Click to expand...
Click to collapse
I'm not a pro. I just learned all of this as I was trying to figure out a way for my problem. I put my phone in download mode and after installing all the necessary drivers Odin was able to recognize my phone and I downloaded a tar.md5 file (I'm not sure whether the file is good or not or at least can't make sure) and selected it as AP and except for auto-reboot and F.reset time. I left everything else unchecked. It started the process and after completion it resetted my phone and everything was back to the way it was. That's the only thing I've tried. Is there anything else I can do?
maxapay said:
I'm not a pro. I just learned all of this as I was trying to figure out a way for my problem. I put my phone in download mode and after installing all the necessary drivers Odin was able to recognize my phone and I downloaded a tar.md5 file (I'm not sure whether the file is good or not or at least can't make sure) and selected it as AP and except for auto-reboot and F.reset time. I left everything else unchecked. It started the process and after completion it resetted my phone and everything was back to the way it was. That's the only thing I've tried. Is there anything else I can do?
Click to expand...
Click to collapse
I still don't know whether you have access to a recovery, which file from where you were attempting to load, or even which ROM you have/had. I have played with a device similar to yours in the past but no enough to make guesses about your particular situation, sorry. I'm afraid someone else will have to jump in and try to help you.
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
I only want my Wogiz WX40 to work properly again. It somehow got into a booting loop and I spent many hours figuring out how to flash it due to drivers acting unexpectedly, incorrect instructions for my device and so on.
I finally got it to flash with stock software I got from needrom using SP Flash Tool. However 1) none of the bottom keys work now and 2) it looks as if the resolution is set too high for the device and I think there is also some slowness when using the phone. I have tried clicking upgrade firmware and formatting the entire flash and using different versions of the software and the result is always the same - the bottom keys not working in particular makes it unusable. I tried downloading the stock rom from another location but after downloading it said I needed a password.
So what is the next thing I can try? I'm at my wit's end here and just want it to work again. Thanks for all help.
Anyone know what I should try? For example what custom RAM + firmware might I want to try? At this point I don't care what it is as long as it works. It's a MT6580 device if that helps.
God, I FINALLY got it working.
In case there's anyone else that runs into this: My mistake was getting the stockrom from needrom, every one of those roms for this phone is bad. Get the rom from shareas.us and use SP Flash Tool to flash it, and even then you have to try to get the one that isn't password protected with no password. Leave the battery in, turn the phone off, use option "format + download" in the software and click download BEFORE you connect the phone, NOW connect the phone and after a little while it will start downloading. Disconnect the phone when it's done and switch it on, it will take a REALLY long time to boot up the first time but it should then work.
That's what came from hours of trying to get it to work. The tutorials etc. online are so confusing, even some incorrect instructions like saying I should take out the battery that are completely false and I would never have gotten it to work if I paid more attention to them. I don't ever want to go through something like that again. I finally have my phone back.
Hey,
I'm pretty new here, so don't hate on my lack of knowledge^^
Maybe I'm even in the wrong sub-forum
(I think there was a sub-forum dedicated to moto x, but this isn't a device-specific issue, so here should be fine - no?)
Got the following problem:
My moto x (2nd gen) is stuck in a loop. I get to the logo-screen, then it goes to "Encryption unsuccessful" and when I click "Reset", it restarts and fails upon trying to reset.
How I got here:
1) A while ago I wanted to encrypt the phone for the lulz (using its' own encryption-tool)
Followed the simple steps, as in having it charged up, but the encryption did not go through.
Don't remember having it to reset at first, it just booted, even though it had bugs after that:
-whenever I charged it, I had problems turning it back on after charging, had to turn off and back on for it to actually work.
-those notifications on top which one can normally open via sliding down, that sliding down did not work after that.
Eventually I did a hard-reset and it fixed the sliding-problem.
Charging also worked fine at first until it did not.
2) I ended up stuck in a boot-loop that went to the logo-screen back and forth (got to logo-screen, restarted, got to logo-screen, restarted, ...)
Tried to soft-/hard-reset using the VOL- and POWER combo.
The hard-reset itself threw some errors at me, something like "can't delete [whatever]".
Still, after a few tries it eventually went past the logo-screen to the encryption-step.
After another few failed resets and emptied cache via recovery-screen, it somehow ignored the encryption-step and turned on the phone (was a fresh version).
3) Worked fine for 1 whole evening, no crashes/glitches/anything until I had to charge it up.
Then it was back to the broken state.
Note: during 2) I tried to boot with a custom recovery-mode(TWRP), but couldn't get it running.
Then I tried to flash it, but anything I tried to install failed.
I had my suspicions, but eventually I got it straightened out: my phone isn't rooted, and the bootloader is locked.
I did get the code to root it via some steps and the motorola service, but the code did not work as it wanted me to unlock the phone first.
From what I've read, to do that I need to get into the settings and unlock/root it...
Funny thing: I can not turn on the phone to get into the settings.
So - anyone got ideas?
Warranty is gone since apparently my tinkering with the locked bootloader and unrooted phone still was visible and they voided the warranty.
Not sure I broke much/anything with that, though, since it DID work at some point after that (even if it was for a few hours before needing recharging)
Therefore I'm open to any suggestions since the alternative stop would be throwing it into the bin^^
Can I unlock the bootloader without having a working system?
Can I root it somehow without having to get into settings (since I can not turn it on in the first place)?
I did a fair share of reading, but most times the guides just assumed that I already rooted it, or forwarded me to a guide where it said "go into settings and spam the build to get advanced options, then simply root/unlock that damn thing". Tried to find a way to unlock/root it without being able to turn it on, but did not get lucky with the search.
If I could unlock and root it, I probably could go from there. Guides are pretty specific and seem to work for most.
Also, I would try the original android version first before searching for any custom systems.
(that is the smartest way to do, right? since I'm just a user and dont plan on doing more hacking/breaking)
Hope all that above wasn't too much to read
Thx for any advice in advance.
Edit:
Well, after what feels like 50 restarts it miraculously did not send me to the "Encryption unsuccessful" but instead booted like it should (as a fresh version, though - so had to backup).
Now I've turned on the thing in the settings so next time it breaks, which I expect to happen by tomorrow, I can flash that sucker.
Still - anyone knows how to enable all that stuff one normally does via settings some way that does not involve successfully booting it?
I mean, there should be a way to root/unlock it without having to turn it on first, right?
Edit2:
As expected, the flashing part was pretty easy, so I'm now sitting with a fresh android 6.0.
Two days in and it's still working fine, haven't had any complications (except battery draining faster then at the very beginning, but I think that's due to it hanging too much on the usb-cable during all those sessions of me trying to fix it - and generally I've had it charge over night a few times to often)
Still would appreciate any advice on how to unlock developer mode and usb-debugging within the bootloader or recovery-mode.