Hi,
So my phone restarted randomly about 20 minutes ago, and when it turned back on, it said "Please enter password". I have a PIN so I can't unlock my device.
I've tried restarting it, connecting it to my PC (which didn't work), unplugging the battery, etc., nothing is working.
I don't know what to do; this has happened before but I can't remember what I did to fix it.
Please help me,
Roisin.
maybe this will help you http://en.miui.com/thread-324522-1-1.html
Related
I have an smartphone Samsung Gravity Smart (SGH-T589), A week ago I turned off, but I accidentally removed the battery. Next day, I tried to turn it on but I could not, It never started. I tried to start the phone in recovery mode but I could not. I connected the phone to my computer to make a hard reset, but my computer never detected the device. I have already installed the drivers from samsung webpage, but nothing happens. I think there is a problem with the boot, but I do not know how to repair that because I can not connect my phone to my computer. If someone knows how to repair my phone plese tell me.
Daniel Sanchez said:
I have an smartphone Samsung Gravity Smart (SGH-T589), A week ago I turned off, but I accidentally removed the battery. Next day, I tried to turn it on but I could not, It never started. I tried to start the phone in recovery mode but I could not. I connected the phone to my computer to make a hard reset, but my computer never detected the device. I have already installed the drivers from samsung webpage, but nothing happens. I think there is a problem with the boot, but I do not know how to repair that because I can not connect my phone to my computer. If someone knows how to repair my phone plese tell me.
Click to expand...
Click to collapse
Probably the battery is dead.Buy a new one
Tapped from my furious ZR
Good night everybody! my dad got this phone a while ago, after like 2 months he told me the phone was going crazy, I checked and was getting FC´s everywhere so get into recovery mode to wipe everything and there´s where problems started. I downloaded stock firmware and installed it but phone wouldn´t boot up, so my dad gave it to a guy that ``fixed it´´ but the problem came back after two weeks or so, the guy ´´fix it ´´ again but when I looked into the phone had no IMEI so didn´t recognized the sim card, the third time the guy got back the IMEI, that was long ago and today when I booted up the phone is having a weird behavior, sometimes gets stucked at the bootloader unlock warning, I restart it and after a couple of times starts the boot up animation but gets stucked at the M and like waving part.
I´ve tried getting into recovery mode but when I press any of those options boots to the warning bootloader. I got it to completley turn on when I pressed the recovery option; not expecting that to happened, but again some force close windows and decided to reboot it to see if would fix it but again to the same place stuck at the warning.
I´ve read many posts here im xda and outside but can´t find a solution. I tried to side load the firmware but looks like the pc doesnt recognize the phone´, when i got it boot up I connected it to the pc but didn´t recognized it, I installed the drivers and still the same.
Guess I need to get it recognized by the pc in order to try to side load a firmware. Sorry for the long post and any mistake, if someone can help to bring back to life this little fella.
Hi all,
I have a Samsung galaxy s2 i9100 which I bought 4 years ago. Two weeks ago my phone accidentally fell on the floor and the screen is cracked . The phone was turned off on that moment. (I had set two different passwords for the screen and the sim, long before the accident). I cannot access the phone . There are many important files and messages stored in the phone. How can get them out of my phone? Please help!
If you have no custom rom you can try and connect the phone to your PC with kies and see if it detect the device you will need to try and turn the phone on while connected.
But I would say your best bet would be to get the screen repaired.
jecatch said:
If you have no custom rom you can try and connect the phone to your PC with kies and see if it detect the device you will need to try and turn the phone on while connected.
But I would say your best bet would be to get the screen repaired.
Click to expand...
Click to collapse
I rooted the phone weeks before the accident. I did Not install any custom rom (so far I understand). I tried connecting the phone with kies (PC), but kies asks me to enter the screen unlock password in the phone before it shows me any file there is No option enter the password inside Kies
Moreover, I cannot use the samsung online service "Find my phone" because it requires the phone to turn on Wi-Fi so that the service can find the phone, I cannot turn-on the Wi-fi in the phone as the screen is un-usable. What can I do to retrieve all files (pic, vdo, messages, contacts etc) from my phone? Please help me....... (p.s: I do not have any money to get the screen repaired)
So starting off, I'm having problems in terms of the bootloader of this phone. I kinda got bored with the stock so I unlocked Max M2's bootloader to install Evolution X ROM (which where recommended by Max M2 users) and yes I did installed it no problem but after a while when finally charging the phone it started to disconnect and reconnect until it finally wont charge. I tried to charge i through Laptop and yes it worked! but after awhile it started to not charge even on a laptop. So I'm starting to convince myself if it is a software problem or the phone itself. Though that's not the case, it connects to the computer when on fastboot mode so I started to think that it is a software problem. So what I find is that when I unlocked the bootloader it started to charge again and so I waited for 2 hours if the charging problem start to come again and yes it did! so what I did is, I relocked the bootloader and yes! IT STARTED TO CHARGE AGAIN!! (though I'm waiting if the problem starts to come again) so anyone also have this problem? or I did something wrong? I decrypted the device when I was rooting but I don't really know if that's the root of the problem?
Please kindly help me if you know, Thanks in advance!!
It seems like this isnt the case at all, so what I did is I tried to change the USB CONFIGURATION to charging and it started to charge again but the problem is the default is not "Charging Only" rather its MTP so how do I change it back to charging only?
I have a pixel 6a that I successfully rooted but when I tried to unroot it something went wrong. When I restarted the phone I got a message saying
Your device is corrupt. It can’t be trusted and may not work properly.” then it was stuck on the Google logo. I managed to get it unstuck but then when it restarted I got the error message again and it shut off. Now the phone will not turn on at all. I tried charging it for hours. I tried forcing it to turn on with every ossible button configuration I could think of. It is completely unresponsive. Please help. I literally just reviewed it from Google Fi a week ago
Cheesymatt661 said:
I have a pixel 6a that I successfully rooted but when I tried to unroot it something went wrong. When I restarted the phone I got a message saying
Your device is corrupt. It can’t be trusted and may not work properly.” then it was stuck on the Google logo. I managed to get it unstuck but then when it restarted I got the error message again and it shut off. Now the phone will not turn on at all. I tried charging it for hours. I tried forcing it to turn on with every ossible button configuration I could think of. It is completely unresponsive. Please help. I literally just reviewed it from Google Fi a week ago
Click to expand...
Click to collapse
Are you on A13?
Did you have, at the minimum, the A13 bootloader on both slots?
What method did you use to uninstall Magisk?
What happens when you connect phone to computer?
Will Android Flash Tool recognize it? If so, use that to flash back to stock.
Try holding the power button down for at least 30 seconds?
If you were on A13 and didn't have the A13 bootloader on both slots, when bootlooping your phone may have reverted to the A12 slot. If so, your device may be a brick due to the new ARB and you should probably RMA it.
Yes it was A13. And nothing happens when I connect it to my laptop. And I'm not sure what you mean by "both slots". My apologies... This is my very first time rooting and trying to unroot a device
I am also using Linux. So I don't really know what other tools I could or should try other than sdk platform tools.
Cheesymatt661 said:
Yes it was A13. And nothing happens when I connect it to my laptop. And I'm not sure what you mean by "both slots". My apologies... This is my very first time rooting and trying to unroot a device
Click to expand...
Click to collapse
Did you do this after updating to A13?
It's a hard brick as per the link in the above post.
But why root, then unroot?
What steps did you take?
It would be helpful to others to find out where you went wrong.
Cheesymatt661 said:
I have a pixel 6a that I successfully rooted but when I tried to unroot it something went wrong. When I restarted the phone I got a message saying
Your device is corrupt. It can’t be trusted and may not work properly.” then it was stuck on the Google logo. I managed to get it unstuck but then when it restarted I got the error message again and it shut off. Now the phone will not turn on at all. I tried charging it for hours. I tried forcing it to turn on with every ossible button configuration I could think of. It is completely unresponsive. Please help. I literally just reviewed it from Google Fi a week ago
Click to expand...
Click to collapse
Why not post this in Pixel 6a forum?
@Cheesymatt661 Okay so you have unlocked bootaloder + fastboot is working right? One of my friend also faced this and what he did was flashed latest (A13) factory images to both A & B slots separately and that's it. It was simple as that for him.