Hello,
A friend gave me his phone so I could root it, having done it before I said no problem, but the problem is his phone was encrypted.
So now he can't get into his phone. The pasword prompt comes up, he types his passsword, a 'Droid' shows and the phone shuts down.
I have tried booting into Recovery but after the bootlogo with the blue recovery text the phone powers off.
Does anybody have a fix?
Thanks in advance for your help
Wamb0 said:
Hello,
A friend gave me his phone so I could root it, having done it before I said no problem, but the problem is his phone was encrypted.
So now he can't get into his phone. The pasword prompt comes up, he types his passsword, a 'Droid' shows and the phone shuts down.
I have tried booting into Recovery but after the bootlogo with the blue recovery text the phone powers off.
Does anybody have a fix?
Thanks in advance for your help
Click to expand...
Click to collapse
You should start by checking the information on the thread of the root you used. When I rooted mine I noted something about not rooting encrypted phones, so... yeah. But anyway - that's where you should go for help.
Related
Dear android experts,
I had CM 5.0.7 installed on my HTC Dream, and I stupidly installed ROM Manager, wanting to upgrate to CM 5.0.8, and used the application to do a backup - after I clicked the 'backup' function, the phone rebooted, and is now stuck on the startup logo (and has been stuck for the last hour). I have already tried pulling out the battery and booting the phone into recovery mode, however it cannot access recovery mode, and still hangs at the startup logo. Is there any way to get past this startup logo, or is there no hope for my phone? Is there any way to push the phone into recovery mode via adb? I am a complete amateur, who follows step-by-step instructions - please help me!
P.S. If this tells you anything, while my phone is stuck at the startup T-mobile logo, if I plug in the USB cable, a message on a red background appears at the top of the 'G1 T-mobile' logo, saying 'FASTBOOT USB'.
P.P.S. In case this is a detail that could help me, while my phone is in Fastboot Mode, I have four options available:
HBoot Mode
Reset Device
Restart to HBoot
Power Down
Could any of these help me?
yeah:) said:
Dear android experts,
I had CM 5.0.7 installed on my HTC Dream, and I stupidly installed ROM Manager, wanting to upgrate to CM 5.0.8, and used the application to do a backup - after I clicked the 'backup' function, the phone rebooted, and is now stuck on the startup logo (and has been stuck for the last hour). I have already tried pulling out the battery and booting the phone into recovery mode, however it cannot access recovery mode, and still hangs at the startup logo. Is there any way to get past this startup logo, or is there no hope for my phone? Is there any way to push the phone into recovery mode via adb? I am a complete amateur, who follows step-by-step instructions - please help me!
P.S. If this tells you anything, while my phone is stuck at the startup T-mobile logo, if I plug in the USB cable, a message on a red background appears at the top of the 'G1 T-mobile' logo, saying 'FASTBOOT USB'.
P.P.S. In case this is a detail that could help me, while my phone is in Fastboot Mode, I have four options available:
HBoot Mode
Reset Device
Restart to HBoot
Power Down
Could any of these help me?
Click to expand...
Click to collapse
i have the same problem.............. did anyone ever help you out??? if the did let me know please!!!
alroco20 said:
i have the same problem.............. did anyone ever help you out??? if the did let me know please!!!
Click to expand...
Click to collapse
This thread is old, and OP is ignorant and wants to blame ROM Manager for his own problems. If you can't get into recovery, chances are you are using one built for another phone. Find the one for the G1.
Or ran into the know issue of cm5.0.7 that fash_image sometimes (more than not) fails.. thus applications using it sometimes fail.
But you have danger spl right? So flash the recovery via fastboot.. and if you don't have fastboot/adb and intended to run these custom roms its about time you installed it.
Hello guys, I'm looking for some help here.
I recently got my update to Lollipop, and today I decided to encrypt my device. The process started alright, and then I left it there encrypting my data. When I came back about 40 minutes later, it asked for my PIN in order to boot the device. After entering it, the screen simply goes back and the phone does nothing.
After leaving it leave for some minutes, I hard resetted the phone by holding the power button, the device started booting up until it asked for my PIN again. I entered it and it's been 1:45h since then. I decided to leave my phone alone for a while to see if anything happens, it's charged and everything. It's still stuck at the same black screen so far.
Any help would be greatly appreciated. I can access recovery, btw. I've never unlocked my bootloader or did any modifications though.
Thanks in advance.
Hi all,
I use CM12 from MacLaw in combination with TWRP 2.8.1.0 recovery for about 3 weeks now.
Yesterday the phone didn't respond properly, was very very slow and I basically couldn't use the phone. It felt like the CPU was at 100% all the time, so unlocking the phone, calling and so was nearly impossible. A reboot (battery removal) didn't solve it, also the pin code for the sim card came after a few minutes while usually this will come right after starting.
So eventually I did a factory reset from the menu as I did on other occasions just to get rid of this kind of problems.
Well, right after the Samsung s3 mini logo I get the TWRP logo and it will be stuck in there, I see it blinking every few seconds and that's it. When I connect the phone to USB I hear it connecting-disconnecting every few seconds (bing-bong, bong-bing sound).
After a while I flashed TWRP using Odin again, this didn't give any problem but it will still hang in this TWRP loop.
I found some references to this problem but no real solutions. Someone suggested to use ADB but I don't know how to do that, nor could I find a suitable guide on this.
Can anyone help me? Or is it bricked somehow?? I suspect not, download mode is still working.
Thanks for any help!
As I said in the title. The phone's memory seems to be read only.
I can access the fastboot mode of the phone and issue commands like flashing the recovery but it doesn't seem to update anything on the phone even though I get the "OKAY" message.
My phone is unlocked and until last night I was running CyanogenMod on it just fine. But now I can't flash a new recovery or access it. I have TWRP installed but everytime I try to boot into recovery the phone gets stuck on the logo screen and flashes every couple of seconds.
If I try to start my phone normally I get the cyanogenmod logo on start up (even after flashing stock) and the phone never actually boots up.
Anyone had the same problem before? If you need more details I'll reply ASAP.
My phone is the retail European XT1068 Dual Sim. Thank you in advance for any help.
Same issue here (I'm MrPowerGamerBR on Reddit), the more I read about trying to fix this issue, the more I start thinking "this phone is dead, move on..."
There isn't no fix for this, the only way to fix is replacing the logic board.
I would like to ask some few solutions from expert people here. My phone was stuck in Boot loop for no apparent reason and cause. So, here's the chronology: I was playing Vainglory and it was still drafting heroes in ranked match. During that time, the phone just got freeze and unresponsive for several seconds. Then, it restarts and there we go. It starts boot loop cycle. I don't know what causes it.
How do I solve this? I need help, please. The Phone is Unlocked Bootloader and it is in root condition. As for the version, it was using 4.88B. I would require step by step detail in solving this boot loop before i decided to go to service center and have it fixed which is possible to remove Unlocked bootloader and root which I do not want that to happen.
Thank you so much in advance.
PS: After shutting it off for 30 min, I tried turning it back on. It does bring me to the home screen but then few seconds, it reboots again and causes boot loop. Nevertheless the case, once Powered by android logo came, I won't be able to bypass that.
Try to hold Volume up and Power while launching the phone - it will bring you into the recovery mode of android. From there you should wipe your phone data - sorry there's no viable solution for you, if it's a software bootloop then it should help you bring the phone to factory state and get rid of issues.
KonikoO said:
Try to hold Volume up and Power while launching the phone - it will bring you into the recovery mode of android. From there you should wipe your phone data - sorry there's no viable solution for you, if it's a software bootloop then it should help you bring the phone to factory state and get rid of issues.
Click to expand...
Click to collapse
Sir, It doesn't show the recovery mode. It is like no recovery exist. It just shows Powered by android logo and then keeps restarting.
did you solve your issue? trying to reboot?
How did it happen?
and How did it solved? Did your phone start then?
I think from TWRP you choose to boot different slot.
So I think you have different Kernel-boot to another system-version