[Q] Cannot wipe or flash anything, stuck in decryption screen. - Verizon HTC One (M8)

I am stuck on the Decyption screen where it says "To start Android, enter your password". I have seen a few threads about this issue but they managed to solve the issue by reflashing or re-unlocking the bootloader. However, I am unable to do any of these things.
I have been on ViperOneM8 for quite a long time now and everything was working fine. I unlock my screen by swiping up on the screen while the screen is off. Felt the vibration to unlock but the screen stays blank. Had to force reboot it to make it work again. A few days later, this exact same issue happened again, but before I was able to reboot the device, it rebooted on its own and went into the said decryption screen. I enter a random word for password and it says, password is correct but data is corrupted; must factory reset to use phone.
Alright, so I have factory reseted, nothing happened. It wiped my data and sd card, same decryption screen.
I've used the bootloader to flash a stock android, I remember it succeeded but restarted to the same screen.
I've used twrp to re-flash multiple roms, all succeeded, restarted to same thing.
I've wiped data, full wipe, you name it, restarted to same thing. Once it reboots it would show the ViperOne boot, so something isn't wiping.
I even went into the phone's data and manually deleted everything in internal storage with my pc, restarted the phone, same thing. Checked the internal storage again, everything that was there got restored.
I've used adb and fastboot to push data, same thing. I've used the dottat .exe installer, goes through the entire process, reboots... same thing.
I've tried reflashing another recovery, success, but it boots into the same recovery.
I've tried doing the SuperCID and going through htcdev to unlock the device again, but it fails when pushing the key. SuperCID also resets whenever I restart the device. I've tried locking the bootloader with fastboot but that fails.
One thing I couldn't do is boot into the RUU mode. 'fastboot oem rebootRUU' doesn't seem to work for me. It reboots the device but boots up and goes into the decryption screen.
When I try the 0P6BIMG with bootloader, it seems to restart before completing the installation now. But I remember it went through successfully before, but still boots into the decryption screen.
It seems like no matter what I do, the phone restores itself to the previous state that it's in. That or nothing is actually affecting the data.
I am at a lost of what to do. I feel like maybe it's a damaged hardware but at the same time I am unsure. Anybody have any suggestions at all?

kyuuku said:
I am stuck on the Decyption screen where it says "To start Android, enter your password". I have seen a few threads about this issue but they managed to solve the issue by reflashing or re-unlocking the bootloader. However, I am unable to do any of these things.
I have been on ViperOneM8 for quite a long time now and everything was working fine. I unlock my screen by swiping up on the screen while the screen is off. Felt the vibration to unlock but the screen stays blank. Had to force reboot it to make it work again. A few days later, this exact same issue happened again, but before I was able to reboot the device, it rebooted on its own and went into the said decryption screen. I enter a random word for password and it says, password is correct but data is corrupted; must factory reset to use phone.
Alright, so I have factory reseted, nothing happened. It wiped my data and sd card, same decryption screen.
I've used the bootloader to flash a stock android, I remember it succeeded but restarted to the same screen.
I've used twrp to re-flash multiple roms, all succeeded, restarted to same thing.
I've wiped data, full wipe, you name it, restarted to same thing. Once it reboots it would show the ViperOne boot, so something isn't wiping.
I even went into the phone's data and manually deleted everything in internal storage with my pc, restarted the phone, same thing. Checked the internal storage again, everything that was there got restored.
I've used adb and fastboot to push data, same thing. I've used the dottat .exe installer, goes through the entire process, reboots... same thing.
I've tried reflashing another recovery, success, but it boots into the same recovery.
I've tried doing the SuperCID and going through htcdev to unlock the device again, but it fails when pushing the key. SuperCID also resets whenever I restart the device. I've tried locking the bootloader with fastboot but that fails.
One thing I couldn't do is boot into the RUU mode. 'fastboot oem rebootRUU' doesn't seem to work for me. It reboots the device but boots up and goes into the decryption screen.
When I try the 0P6BIMG with bootloader, it seems to restart before completing the installation now. But I remember it went through successfully before, but still boots into the decryption screen.
It seems like no matter what I do, the phone restores itself to the previous state that it's in. That or nothing is actually affecting the data.
I am at a lost of what to do. I feel like maybe it's a damaged hardware but at the same time I am unsure. Anybody have any suggestions at all?
Click to expand...
Click to collapse
Sounds like you have one of the few that have been popping up where the entire phone becomes write protected.
Before running the ruu run the following fastboot commands.
Fastboot oem task 28
Fastboot oem task 29
If any errors re-run the command.
Then run ruu.

dottat said:
Sounds like you have one of the few that have been popping up where the entire phone becomes write protected.
Before running the ruu run the following fastboot commands.
Fastboot oem task 28
Fastboot oem task 29
If any errors re-run the command.
Then run ruu.
Click to expand...
Click to collapse
I tried those commands and it looks successful, but once I rebootRUU it would just reboot and load to the decryption screen again.
I also tried the 0P6BIMG method after those commands, no luck.

kyuuku said:
I tried those commands and it looks successful, but once I rebootRUU it would just reboot and load to the decryption screen again.
I also tried the 0P6BIMG method after those commands, no luck.
Click to expand...
Click to collapse
Sounds like your phone did end up write protected. You need a new motherboard.
The ones I have seen like this don't even allow you to lock the boot loader or turn s back on either.

dottat said:
Sounds like your phone did end up write protected. You need a new motherboard.
The ones I have seen like this don't even allow you to lock the boot loader or turn s back on either.
Click to expand...
Click to collapse
Ahh that's too bad. It was what I expected though.
Thank you anyway for the help!

Related

[Q] Need a little help!

Hey guys,
On Friday my Nexus S started acting buggy, freezing up on me periodically. I woke up Saturday to find the phone (charging) completely unresponsive with the four face buttons lit up. I did a hard reset, but it just loads up the start "GOOGLE" screen and stays there, won't actually load the operating system.
I've booted into recovery mode, done a factory reset, wiped the cache partition, but nothing seems to work. The bootloader is not unlocked and I can't seem to get it unlocked because ADB won't even acknowledge that the phone is plugged in.
I'm completely stumped here and I now seem to own a real expensive paper-weight. I haven't done any customizations, just used the phone completely stock since I bought it in December.
Any advice would be greatly appreciated!
Thanks
Check this out ...same problem i think
Danchr said:
Hey guys,
On Friday my Nexus S started acting buggy, freezing up on me periodically. I woke up Saturday to find the phone (charging) completely unresponsive with the four face buttons lit up. I did a hard reset, but it just loads up the start "GOOGLE" screen and stays there, won't actually load the operating system.
I've booted into recovery mode, done a factory reset, wiped the cache partition, but nothing seems to work. The bootloader is not unlocked and I can't seem to get it unlocked because ADB won't even acknowledge that the phone is plugged in.
I'm completely stumped here and I now seem to own a real expensive paper-weight. I haven't done any customizations, just used the phone completely stock since I bought it in December.
Any advice would be greatly appreciated!
Thanks
Click to expand...
Click to collapse
Can you get to fastboot?
Danchr said:
Hey guys,
On Friday my Nexus S started acting buggy, freezing up on me periodically. I woke up Saturday to find the phone (charging) completely unresponsive with the four face buttons lit up. I did a hard reset, but it just loads up the start "GOOGLE" screen and stays there, won't actually load the operating system.
I've booted into recovery mode, done a factory reset, wiped the cache partition, but nothing seems to work. The bootloader is not unlocked and I can't seem to get it unlocked because ADB won't even acknowledge that the phone is plugged in.
I'm completely stumped here and I now seem to own a real expensive paper-weight. I haven't done any customizations, just used the phone completely stock since I bought it in December.
Any advice would be greatly appreciated!
Thanks
Click to expand...
Click to collapse
Is this guy posting under different usernames?
Anyways here's what I wrote to another person, pretty much the same thing:
If you can get into bootloader and recovery, you're not bricked.
ADB is used when Android is booted up.
Fastboot is used in bootloader.
Get Fastboot working (proper drivers etc)
Go into bootloader on your phone.
run 'fastboot devices' if your phone and serial number shows up, fastboot is working.
run 'Fastboot oem unlock'
then flash clockworkmod recovery 'fastboot flash recovery filenameofrecovery.img'
boot into recovery.
mount the internal sd. search for a stock nandroid backup in the forums, copy it over to the internal sd.
umount, go back to main menu of cwm recovery and restore that nandroid backup.
reboot. if it boots up and stuff, shut down phone, go back to bootloader and 'fastboot oem lock' to relock bootloader and you should be at stock.

[Q] Can't use phone -- Type password to decrypt message

I'm at a loss here. I was using my phone as normal today, no issues all day. When I tried loading Facebook to respond to a comment I suddenly started getting a lot of stopped process errors. Pretty much all were GAPPS processes. Then my phone rebooted. After it booted back up (no issues, no subsequent reboots, saw the HTC screen and the ViperXL screen), my phone loads to an empty lock screen with the default ViperXL background and just the ring. The phone is also now in Airplane mode and showing the time to be 5 hours ahead. When I unlock the phone, I am met with a screen that tells me to "Type password to decrypt". I have never created a password. Nothing works. I can only make emergency calls. No amount of rebooting or wiping cache or dalvik in TWRP works. I have not updated this phone recently and when I try to restore from backup none of my backups show up in the TWRP folder. I cannot do a factory reset as I receive errors when attempting to mount the SD card. I've read several other forum posts for similar issues for different devices but none of what they try works. My computer recognizes when the phone is connected, but it does not mount the SD Card and I cannot put the ROM .zip file back onto it to reinstall from recovery. I cannot adb as it doesn't recognize the device as being connected. I can initiate fastboot and it does see my device, but when I try to erase the userdata partition or anything else I receive an error that states "failed (remote: not allowed)". All instincts would lead me to believe it's a locked bootloader, but the bootloader screen still shows as UNLOCKED. I am S-Off on HBOOT 1.14.0002. Currently ViperXL 3.2.6 is installed with ElementalXL 5.4 for the kernel and the AT&T 3.18 Radio. Again, I have not TOUCHED my setup in over 3 weeks, with the last update being the updated radio. I am freaking out without any means to communicate with my family and just want an operational phone again. Any ideas/thoughts/suggestions would be greatly appreciated.
Pdj7969 said:
I'm at a loss here. I was using my phone as normal today, no issues all day. When I tried loading Facebook to respond to a comment I suddenly started getting a lot of stopped process errors. Pretty much all were GAPPS processes. Then my phone rebooted. After it booted back up (no issues, no subsequent reboots, saw the HTC screen and the ViperXL screen), my phone loads to an empty lock screen with the default ViperXL background and just the ring. The phone is also now in Airplane mode and showing the time to be 5 hours ahead. When I unlock the phone, I am met with a screen that tells me to "Type password to decrypt". I have never created a password. Nothing works. I can only make emergency calls. No amount of rebooting or wiping cache or dalvik in TWRP works. I have not updated this phone recently and when I try to restore from backup none of my backups show up in the TWRP folder. I cannot do a factory reset as I receive errors when attempting to mount the SD card. I've read several other forum posts for similar issues for different devices but none of what they try works. My computer recognizes when the phone is connected, but it does not mount the SD Card and I cannot put the ROM .zip file back onto it to reinstall from recovery. I cannot adb as it doesn't recognize the device as being connected. I can initiate fastboot and it does see my device, but when I try to erase the userdata partition or anything else I receive an error that states "failed (remote: not allowed)". All instincts would lead me to believe it's a locked bootloader, but the bootloader screen still shows as UNLOCKED. I am S-Off on HBOOT 1.14.0002. Currently ViperXL 3.2.6 is installed with ElementalXL 5.4 for the kernel and the AT&T 3.18 Radio. Again, I have not TOUCHED my setup in over 3 weeks, with the last update being the updated radio. I am freaking out without any means to communicate with my family and just want an operational phone again. Any ideas/thoughts/suggestions would be greatly appreciated.
Click to expand...
Click to collapse
You're s-off. Boot bootloader/fast boot and ruu
Sent from my One X using xda app-developers app
We're you connected to an exchange server? It is the only thing that I know of that could wipe or encrypt your phone.
Sent from the HOXL dimension of S-OFF
Well this is a new one on me. Not sure what happened or how I did it, but as you can see below, I managed to get my phone working again. I left it alone for a bit while I had dinner. Once done, I tried once again to do a factory reset in TWRP and all indications led me to believe that it had failed once again (received a failed notification). I then rebooted the phone and this time it brought me to the HTC setup screens where I was to enter all my info. I got past that and connected to my wifi. I then noticed my phone wouldn't get a network connection with AT&T so I downloaded and refreshed the 3.18 radio and after reboot it connected to LTE without issue. Since I lost all my data I am now in the process of reinstalling my apps. I had been meaning to do a full wipe eventually as things were getting a little sluggish, so I guess this just kicked me in the pants a bit. Bummed I lost my photos I took today, but what can you do?
To answer your question, no, I do not have it setup with Exchange. My company does not allow Android devices to connect to Exchange, only iPhones via ActiveSend so that wasn't it. This has happened to several others, but they were always in the act of flashing something or making changes when it happens, never just normal use and a magical reboot kills everything. This of course makes me nervous that it'll happen again, but seeing as I am in the market for the One, I might not have to worry much longer. Thanks for the suggestions.
Sent from my HTC One X using xda app-developers app
As long as you can get into bootloader you can always run the ATT 3.18 RUU.
Sent from the HOXL dimension of S-OFF

Bricked or hardware issue

I was charging my phone overnight. In the morning I realized it didn't charge, I tried to turn it on and it gets stuck on the HTC screen.
I was running Viper One 3.21, I tried rebooting, entered recovery, tried to reinstal a nandroid, got stuck on the screen again.
Tried reinstalling ViperOne same problem.
Here's what I know:
Fastboot will NOT work, while I can get to fastboot, any time I reboot the phone it gets stuck.
I can't get to RUU (because it wont go past the HTC screen).
adb sideload will not work
I've let the battery drain, fully charged it; no change.
I tried wiping and doing a factory reset but it just gets stuck on the reboot, I also noticed on the File manager within TWRP that my phone was never wiped.
Any ideas?
SS823 said:
I was charging my phone overnight. In the morning I realized it didn't charge, I tried to turn it on and it gets stuck on the HTC screen.
I was running Viper One 3.21, I tried rebooting, entered recovery, tried to reinstal a nandroid, got stuck on the screen again.
Tried reinstalling ViperOne same problem.
Here's what I know:
Fastboot will NOT work, while I can get to fastboot, any time I reboot the phone it gets stuck.
I can't get to RUU (because it wont go past the HTC screen).
adb sideload will not work
I've let the battery drain, fully charged it; no change.
I tried wiping and doing a factory reset but it just gets stuck on the reboot, I also noticed on the File manager within TWRP that my phone was never wiped.
Any ideas?
Click to expand...
Click to collapse
Sorta sounds like one of the bricked ones where the entire emmc goes write protected. If you can't get fastboot or ruu mode and have no warranty left I can take a look at it for you. I'm in PA so it wouldn't take long to mail it here.
Not sure how it got bricked, it has been over a month since I flashed anything.
I am able to use adb sideload, but any file I use it says is corrupted.
Could I partition part of the drive and try to instal from there?
What part of PA are you in?
SS823 said:
Not sure how it got bricked, it has been over a month since I flashed anything.
I am able to use adb sideload, but any file I use it says is corrupted.
Could I partition part of the drive and try to instal from there?
What part of PA are you in?
Click to expand...
Click to collapse
I am down in the York/Harrisburg/Lancaster area. You don't want to partition emmc manually.

Nexus 5 not starting

Urgent help reqd
randomly my nexus 5 restarted
google came on screen and now only those four animated circles are showing up and the phone doesnt go further
went in bootloader but cant wipe cache, cant format, or anything else from there.
usb debuggng must be off as far as i remember
trying to flash through sdk manager. have downloaded image. but stops at "waiting for device" in cmd and it doesnt go any further than that. even tried doing it manually through cmd.
when the phone is connected it is showing the drivers but it isnt installng and can see the yellow exclamation.
manually downloaded the drivers and tried installing manually but shows drivers are up to date.
uninstalled driver and reinstalled but same issue. it is connected to usb 2.0.
now how do i get it to work?
I have tried all the options i could search for on this forum but none of them solved my issue.
Is the bootloader unlocked?
How do i check that?
Ok got it
It is locked
How do i unlock?
I checked some unlocking bootloader threads but they all require usb debugging to be on.
My phone is not starting at all so i cannot do that
How do i go about it now
Tried nexus root toolkit. It isnt detecting the device.
Unlocking will wipe you device.
Google themselves have a guide on how to flash, not sure why you are using toolkits.
Also, you will wipe your device, if you haven't already. Make sure you have the right drivers, make sure you get the device to come up under "fastboot devices"
Already tried all methods mentioned by google or xda.
If you read my initial post my phone is not getting detected as well but shows installing drivers when connected but the installation fails.
Manually install the correct drivers.
Tried that but i get the error that you already have latest drivers. But its not detecting the phone
Try removing the drivers and reinstalling
Also, try different USB ports and cables.
Did all of that a number of times. Still no luck
Other phones are getting connected and detected just fine.
useruser12 said:
Urgent help reqd
randomly my nexus 5 restarted
google came on screen and now only those four animated circles are showing up and the phone doesnt go further
.
Click to expand...
Click to collapse
Hi all, i have a similar problem
this morning my n5 boots into "optimizing apps", but stops when reach around 15/20 apps and reboot (3 or 4 times)...
Now, only keeps in android animation like useruser12.
I can see my data in TWRP, battery 95%...
I wipe cache/dalvik... nothing
I reflash the kernel (ElementalX 6.17), still nothing
Any ideas?
PS: latest news. After make a backup, I made a factory reset and restore a system-boot-cache partition from old backup. Now the phone boots but i hate lose all my data xD. I want try to solve my problem using my "corrupted" backup for avoid losing data. If that fails, I can always restore this functional backup. Any ideas again?
Used the nexus root toolkit.managed to unlock bootloader but immediately the device reboots and goes into the bootloop again.
Tried the flash stock + unroot function as well which detected my factory image and everything went smooth till it came back to unlocking the bootloader and rebooting the device after that and again went into the bootloop
Though i have installed the drivers, on reboot windows 7 automatically starts installing the mtp usb device driver but fails. Manually downloaded the drivers and installed as well.
Still its not worked and whatever i do it comes back and get stuck at the bootloop.
Any expert can give a solution? Thanks
After unlocking the bootloader, does the bootloader relock when the phone is rebooted? If it does, the memory chip is defective.
Phone doesnt reboot completely.goes into a loop after the google logo and doesnt go further.
If i switch off the phone midway here without it booting up and then restart the bootloader then its locked again.
But what i read was that the process of complete reboot needs to finish and i need to turn on usb debugging. So is it because of that the bootloader locks again?
Anyways, this what im facing
Dalamar666 said:
Hi all, i have a similar problem
this morning my n5 boots into "optimizing apps", but stops when reach around 15/20 apps and reboot (3 or 4 times)...
Now, only keeps in android animation like useruser12.
I can see my data in TWRP, battery 95%...
I wipe cache/dalvik... nothing
I reflash the kernel (ElementalX 6.17), still nothing
Any ideas?
PS: latest news. After make a backup, I made a factory reset and restore a system-boot-cache partition from old backup. Now the phone boots but i hate lose all my data xD. I want try to solve my problem using my "corrupted" backup for avoid losing data. If that fails, I can always restore this functional backup. Any ideas again?
Click to expand...
Click to collapse
Lucky that you could do a factory reset. I wasnt even able to do that from the bootloader.
useruser12 said:
Lucky that you could do a factory reset. I wasnt even able to do that from the bootloader.
Click to expand...
Click to collapse
Sorry, i did it via TWRP.
If the bootloader relocks itself upon reboot, it's the memory chip that is damaged.

[HELP] Honor 7x/Mate SE Soft Brick?

So I was putting together a flashable zip for downgrading to Nougat, and when I rebooted I must have erased something I shouldn't have, because the screen went black. I have no idea what i could have done but when i force restart, it makes the pc disconnect sound and three seconds later, it reconnects. I can't reboot to bootloader or recovery, much less system, but strangely adb commands still show that my phone is is fastboot mode. I ran the Huawei Multitool with files I know for sure were correct, and hit unbrick. There were no errors and everything flashed correctly, or so it said. Once again I attempted to reboot but to no avail. The screen stays black.
Can anyone help me out here??? I don't know what happened. I don't think it's hardbricked right? I can still use fastboot.
Thanks!

Categories

Resources