Hi all,
I'm hoping to get some advice/help from all you experts for my HTC One M8.
It's stock, hasn't been changed or modified in anyway. After the battery went flat and it was recharged it came up with "Your phone is encrypted - enter your screen lock password". I used to have a password months ago but took it off. Anyway I put the password in and it comes up with this..."Decryption unsuccessful. The password you entered is correct, but unfortunately your data is corrupt. To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account." At this point I'm swearing as it doesn't look good. I hit the "reset phone" button hoping it will magically work but after a couple of minutes and a sickening red triangle with an exclamation mark in the middle, it returns to the "your phone is encyrpted" page.
So here I am, pleading for help as its magically only two months outside of warranty and my carrier doesn't want to know me.
Please help!
Thank you in advance
UPDATE
UPDATE:
I have tried going through the htcdev unlock bootloader in the effort to get TWRP and hopefully some success from there but it doesn't seem to finish the unlock process. I get to the last step where I accept the unlock on the phone and it resets back to the same encyrpted/corrupted screen. Using the power and volume down I can see in the boot menu that it is still ***locked***.
Is there ANY other way to unlock bootloader and install TWRP?
same with me
unable to mount anything, cant flash recovery(it flashes, but nothing changes)
cant format, when phone boots it says that "phone is encrypted bla bla bla, reset device just reboots back to twrp)
cant boot into oem rebootRUU, it just reboots phone=(
olvrick said:
device just reboots back to twrp)
Click to expand...
Click to collapse
If you can get into TWRP, that's a good thing. Go to Wipe section, and tap the button "Format Data". This usually fixes the storage corruption issue.
The OP has a different version of this. He doesn't have custom recovery, and in this condition, I don't think you can flash TWRP, anyway. So unlocking the bootloader is probably not going to help matters. Try to RUU, if your version has one.
Related
Hi all, first time poster long time reader.
I'm stuck, tried a few things and I don't know what to do next. I'll try and keep it brief..
One X international, sim unlocked, Stock ROM 3.20.401.31, bootloader locked
So, I was using Google Maps navigating a place I never visited trying to get somewhere I have never been, the One X completely froze on me Did a hard reset by holding the power button down and then I powered the phone on again, the phone then started up straight in the the bootloader, before that that the HTC logo appeared with some red writing stating it was in dev mode..weird? (I've rooted phones before an never seen this).
- In the bootloader I tried factory reset and entering recovery they all just brought me back to the bootloader menu
- Tried locating the RUU for my software version in the hope I could just reflash that, couldn't find it anywhere
- Battery got way low so ran a battery script to continually reboot the phone, works well and gets me to 10%
- Thought I could try and get a custom recovery on the phone no such luck because ...
- Bootlaoder won't unlock, fasboot gives an error "Too many links" but I believe this is nothing to worry about. Phone reboots with "locked" and "security warning" at the top of the bootloader screen
- Now where do I go?
Any suggestions would be great, as far as I can tell I'm screwed unless I get that bootloader unlocked.
Keep up the great work guys.
H
I give up, I think I'm going to have to ring the insurance company, no matter how many times I try to unlock the bootloader I get nowhere.
did anyone get anywhere with this problem?
hybridised said:
I give up, I think I'm going to have to ring the insurance company, no matter how many times I try to unlock the bootloader I get nowhere.
Click to expand...
Click to collapse
did u get anywhere with this?
I have an htc one as stated above. It is rooted and has s-off but at the time things went wrong I was running my stock rom.
Yesterday when I went to pause my music my screen froze. I tried turning my phone off and when I attemtep to reboot it all I got was the htc white logo screen. It will remain on this screen until I turn the phone off.
I can enter the bootloader but the options don't work (reboot only turns the phone off, factory rest freezes the bootloader) I have tried everything to fix this, from locking the bootloader and using an RUU exe (locking the bootloader failed) to reflashing the recovery (gave me the error "remote image update error).
The thing that I really don't understand is why this happened, I wasn't even doing anything and my phone just crapped out on me.
I need this phone back and I don't know what to do, any help is greatly appreciated.
Thanks!
Oh, and the best part is that all of this happened AFTER I already filed a warranty claim for the phones faulty mic. My new device comes tomorrow and if I send them this one back I'll be out 600 bucks.
Is there any way to fix this?
wolfsummers said:
I have an htc one as stated above. It is rooted and has s-off but at the time things went wrong I was running my stock rom.
Yesterday when I went to pause my music my screen froze. I tried turning my phone off and when I attemtep to reboot it all I got was the htc white logo screen. It will remain on this screen until I turn the phone off.
I can enter the bootloader but the options don't work (reboot only turns the phone off, factory rest freezes the bootloader) I have tried everything to fix this, from locking the bootloader and using an RUU exe (locking the bootloader failed) to reflashing the recovery (gave me the error "remote image update error).
The thing that I really don't understand is why this happened, I wasn't even doing anything and my phone just crapped out on me.
I need this phone back and I don't know what to do, any help is greatly appreciated.
Thanks!
Click to expand...
Click to collapse
Additionally, everything is still unlocked (bootloader says unlocked, still have s-off) and there is no tamper evidence either.
wolfsummers said:
Additionally, everything is still unlocked (bootloader says unlocked, still have s-off) and there is no tamper evidence either.
Click to expand...
Click to collapse
When you enter your boot loader, what does the following command give you: fastboot devices
If you get your phone in response, you are not out of hope.
Sent from my Lunar Ecliptic One.
After an entirely random error saying my phone is somehow Encrypted, I went ahead and did a factory reset which didn't help. The phone was still booting into the same screen asking me for a code to Decrypt the data. So after some "quick" reading on these forums I've decided to RUU to stock. But the file I've chosen, even though it matched my version it was a Firmware, while the phone was S-ON. The device had never been Rooted or tampered with previously.
So now the phone does not boot at all. I've tried every button combination, but nothing seems to work. If I plug in the phone to charge the orange light flashes, endlessly. Even after I've left the device to charge for 6hours, the orange light still flashes.
When I plug in the phone to my PC, all I get it seems is this new device: QHSUSB_BULK, which shows with an exclamation mark next to it. I've read similar threads for different phones where they've unbricked devices while they were in this mode, is that even possible? I can hear Windows recognizing a device was plugged in, and if I press Power+VolumeUP, it will disconnect the phone and reconnect it, at least based on the sounds Windows is playing. The screen is Black at all times.
How badly have I bricked this device and is there any hope to revive it? Thanks to everyone who chimes in on this.
arrayy said:
After an entirely random error saying my phone is somehow Encrypted, I went ahead and did a factory reset which didn't help. The phone was still booting into the same screen asking me for a code to Decrypt the data. So after some "quick" reading on these forums I've decided to RUU to stock. But the file I've chosen, even though it matched my version it was a Firmware, while the phone was S-ON.
Click to expand...
Click to collapse
Most likely it's a soft break. So you can fix it. First of all get yourself a working usb cable. Your's maybe broken.
Your phone's data partition had been encrypted. It never boots up completely without lux password. You could've format the data partition with a custom recovery such as TWRP. Instead you tried the reflash firmware but obviously it didn't finish and failed. All you need is reflash again but doing it correct way so it can finish. Your old data is gone atm. You will have factory reset phone at the end. Before giving you any instructions, you need to answer a few questions so anyone can help.
Have you ever updated your phone to marshmallow which is android 6? If no: You can recover it with voidzero's wonderful answer titled back to stock. Follow that exactly. If yes you can't flash old versions since they are using different bootloaders. Also you will have to reflash it manually. It's long and difficult for anyone who is new. If you don't know if it was updated. Just boot into bootloader then Fastboot mode, connect usb. Then use htc's Fastboot. Run htc_fastboot getvar all command. Paste output here.
Thanks for replying, risyasin.
Yes, I did update to Android 6. The problem is I'm not able to boot into the bootloader using the Power+VolumeUP keys, or any other combination.
Instead of flashing the RUU, or maybe turning to S-OFF(I still don't know if this would've made a difference), I flashed a firmware, one that matched my version. This is the exact filename: 0PKVIM[email protected]60201_20.05_018_F_release_479349_combined_signed
I've renamed it to 0PKVIMG.zip and booted using the Power+VolumeUP keys. For whatever reason, everything went OK, no errors whatsoever. In the end it told me to press Power to reboot the phone. I've pressed Power and nothing happened since.
If anyone can help me figure this out, I'd be forever grateful.
arrayy said:
Thanks for replying, risyasin.
Yes, I did update to Android 6. The problem is I'm not able to boot into the bootloader
Click to expand...
Click to collapse
That is a big problem. I assume you never tried to go S-OFF (which is dangereous). While phone was S-ON. You could always boot into bootloader. That's one of the purpose of staying S-ON.
Combination is Power + Volume down. But if your phone is up & somehow can not continue to boot. eg: stuck at reading system or kernel etc. You can do a hard reset which is pressing Volume up + volume down + power for at least 15 seconds. phone will shut down. then you can try bootlader combination. Make sure it's has power on with light at screen edges you must look at carefully. After trying this if you still can not see bootloader. That's a problem beyond my experiences, so I don't have any idea to fix it.
I have never tried the firmware you have used. Maybe that firmware is not usable, broken or even dangerous.
We need to confirm that here. if anyone else tried and brick their phone with that.
My XL is stuck in a boot loop that I haven't found described anywhere. It begins with the bootloader unlocked warning screen then goes to the white "Google" boot screen, but within one second the screen goes black, waits about 10 seconds and runs through that cycle again. It also randomly (it seems) does the "Writing to EX4 file" screen before the bootloader unlocked warning screen.
It will cycle through this sequence forever if it's plugged in but when not plugged in it will seemingly power off after a random number of cycles. However, powering on does not require holding down the power button - it jumps directly to the beginning of the cycle, sometimes at the bootloader unlocked screen and sometimes at the EX4 screen.
At no point does my Windows 10 PC show the phone as being attached when plugged in to USB. Also, no combination or duration of the phone's physical buttons affect this in any way.
I was following the steps in this article and had just performed the second-last line in the post, "Reboot into the installed recovery." That's when the cycle started. Prior to the step "In TWRP, install twrp.zip" everything was working correctly, though I hadn't rooted yet, of course. I didn't reboot normally in between those two steps, so I can't say which of them caused the problem.
I'm running Android Update, 7.1.2 N2G47E and had been before beginning the procedure. It came from the OTA update and had unrooted the phone from the previous version.
Any and all help will be rewarded with 137 Antique, Pre-Web Internet Points and The Thanks of a Grateful Nation™.
I would fastboot latest factory image.
Just hold vol- when a reboot comes it will go into bootloader.
piz333 said:
My XL is stuck in a boot loop that I haven't found described anywhere. It begins with the bootloader unlocked warning screen then goes to the white "Google" boot screen, but within one second the screen goes black, waits about 10 seconds and runs through that cycle again. It also randomly (it seems) does the "Writing to EX4 file" screen before the bootloader unlocked warning screen.
It will cycle through this sequence forever if it's plugged in but when not plugged in it will seemingly power off after a random number of cycles. However, powering on does not require holding down the power button - it jumps directly to the beginning of the cycle, sometimes at the bootloader unlocked screen and sometimes at the EX4 screen.
At no point does my Windows 10 PC show the phone as being attached when plugged in to USB. Also, no combination or duration of the phone's physical buttons affect this in any way.
I was following the steps in this article and had just performed the second-last line in the post, "Reboot into the installed recovery." That's when the cycle started. Prior to the step "In TWRP, install twrp.zip" everything was working correctly, though I hadn't rooted yet, of course. I didn't reboot normally in between those two steps, so I can't say which of them caused the problem.
I'm running Android Update, 7.1.2 N2G47E and had been before beginning the procedure. It came from the OTA update and had unrooted the phone from the previous version.
Any and all help will be rewarded with 137 Antique, Pre-Web Internet Points and The Thanks of a Grateful Nation™.
Click to expand...
Click to collapse
Sounds like you were coming from the April 2017 update to the May 2017 OTA update. The May update included a new bootloader which performs additional verification on the boot image. I suspect that when you installed TWRP and rebooted, the May bootloader detects the changes TWRP installation made to your boot image and aborts the boot process resulting in your bootloop. Additional detail and information can be found in the linked thread and solution should be towards the end of the thread. You have a few options I think (assuming you can get into fastboot/recovery mode) - you can temporarily resolve by reverting back to the April 2017 bootloader which does not have the additional boot verification procedure or you can follow the steps to flash Chainfire's VerifiedBootSigner.zip if you prefer to get fully on the May update (including the May bootloader). Details are in the thread below. Good luck!
https://forum.xda-developers.com/pixel-xl/how-to/images-t3599709
piz333 said:
My XL is stuck in a boot loop that I haven't found described anywhere. It begins with the bootloader unlocked warning screen then goes to the white "Google" boot screen, but within one second the screen goes black, waits about 10 seconds and runs through that cycle again. It also randomly (it seems) does the "Writing to EX4 file" screen before the bootloader unlocked warning screen.
It will cycle through this sequence forever if it's plugged in but when not plugged in it will seemingly power off after a random number of cycles. However, powering on does not require holding down the power button - it jumps directly to the beginning of the cycle, sometimes at the bootloader unlocked screen and sometimes at the EX4 screen.
At no point does my Windows 10 PC show the phone as being attached when plugged in to USB. Also, no combination or duration of the phone's physical buttons affect this in any way.
I was following the steps in this article and had just performed the second-last line in the post, "Reboot into the installed recovery." That's when the cycle started. Prior to the step "In TWRP, install twrp.zip" everything was working correctly, though I hadn't rooted yet, of course. I didn't reboot normally in between those two steps, so I can't say which of them caused the problem.
I'm running Android Update, 7.1.2 N2G47E and had been before beginning the procedure. It came from the OTA update and had unrooted the phone from the previous version.
Any and all help will be rewarded with 137 Antique, Pre-Web Internet Points and The Thanks of a Grateful Nation™.
Click to expand...
Click to collapse
Just started with me today too.
I cannot get into recovery or boot loader
rebooting using the hard button just brings up this Dump to EXT4 and then into the ROM that is havnig a ish ton of force closes.
My plan is to back up some stuff I need to copy off the phone and then start factory reset from within settings.
EDIT:
I was rooted running stock
All i did was run a backup in TWRP
issues started after reooting.
Once i factory reset and re Root i will see if I can restore backup, maybe
sb1893 said:
Sounds like you were coming from the April 2017 update to the May 2017 OTA update. The May update included a new bootloader which performs additional verification on the boot image. I suspect that when you installed TWRP and rebooted, the May bootloader detects the changes TWRP installation made to your boot image and aborts the boot process resulting in your bootloop. Additional detail and information can be found in the linked thread and solution should be towards the end of the thread. You have a few options I think (assuming you can get into fastboot/recovery mode) - you can temporarily resolve by reverting back to the April 2017 bootloader which does not have the additional boot verification procedure or you can follow the steps to flash Chainfire's VerifiedBootSigner.zip if you prefer to get fully on the May update (including the May bootloader). Details are in the thread below. Good luck!
https://forum.xda-developers.com/pixel-xl/how-to/images-t3599709
Click to expand...
Click to collapse
I had forgotten that after I booted normally just before installing TWRP, the May OTA happened to arrive and I went ahead and installed it. Then the problem started after I installed TWRP. I used @mikaole's advice and got into bootloader (can't believe I hadn't done that, given all the button combinations I'd tried).
I re-flashed the April update and now the behavior is exactly the same except that the white Google boot screen lasts about 5 seconds and after a few boot tries I land on the "No command" screen. That sits for about a minute and boots again, landing again on "No command." Power+vol-up gets me to recovery mode but all I can do is go to bootloader or get back to "No command." I tried a factory reset, same result. I tried re-flashing April again, same result. Now I think I have the May bootloader with all else April.
I ran this:
Code:
fastboot set_active a
because I noticed that flashing the bootloader was always going to b. After flashing the bootloader again and seeing it go to a, the phone boots normally. I'm going to let the May update happen and wait to root again until after that.
One thing, I don't think the link you provided is the one you intended - there's none of the info you said would be there.
This has been very helpful. You and @mikaole got me through this. Thanks!
piz333 said:
I had forgotten that after I booted normally just before installing TWRP, the May OTA happened to arrive and I went ahead and installed it. Then the problem started after I installed TWRP. I used @mikaole's advice and got into bootloader (can't believe I hadn't done that, given all the button combinations I'd tried).
I re-flashed the April update and now the behavior is exactly the same except that the white Google boot screen lasts about 5 seconds and after a few boot tries I land on the "No command" screen. That sits for about a minute and boots again, landing again on "No command." Power+vol-up gets me to recovery mode but all I can do is go to bootloader or get back to "No command." I tried a factory reset, same result. I tried re-flashing April again, same result. Now I think I have the May bootloader with all else April. How do I revert the bootloader?
Also, I don't think the link you provided is the one you intended - there's none of the info you said would be there.
This has been very helpful so far. Thanks!
Click to expand...
Click to collapse
They flashing all the parts of the image manually. Something like this happened to a buddy of mine and using the flash all wouldn't fix. He couldn't get the device to boot until he did all the images manually.
piz333 said:
I had forgotten that after I booted normally just before installing TWRP, the May OTA happened to arrive and I went ahead and installed it. Then the problem started after I installed TWRP. I used @mikaole's advice and got into bootloader (can't believe I hadn't done that, given all the button combinations I'd tried).
I re-flashed the April update and now the behavior is exactly the same except that the white Google boot screen lasts about 5 seconds and after a few boot tries I land on the "No command" screen. That sits for about a minute and boots again, landing again on "No command." Power+vol-up gets me to recovery mode but all I can do is go to bootloader or get back to "No command." I tried a factory reset, same result. I tried re-flashing April again, same result. Now I think I have the May bootloader with all else April.
I ran this:
Code:
fastboot set_active a
because I noticed that flashing the bootloader was always going to b. After flashing the bootloader again and seeing it go to a, the phone boots normally. I'm going to let the May update happen and wait to root again until after that.
One thing, I don't think the link you provided is the one you intended - there's none of the info you said would be there.
This has been very helpful. You and @mikaole got me through this. Thanks!
Click to expand...
Click to collapse
Glad you got it working. I checked and I did link the thread I intended to. Starting at post #57 onward from that thread has the information on how to update to the May update and leverage Chainfire's VerifiedBootSigner.zip.
Thx,
S
Pixel bootloop
Hey guys, this is the only thread thqt i found here on XDA about pixel and pixel XL bootloop issue.
I'm about to buy a used Pixel 1st gen phone for really great deal, because it is in this bootloop. As the owner sad, it was on the Oreo upgrade. I'm wondering if its possible to fix it... What you guys say?
Thanks!!
rosendomurilo said:
Hey guys, this is the only thread thqt i found here on XDA about pixel and pixel XL bootloop issue.
I'm about to buy a used Pixel 1st gen phone for really great deal, because it is in this bootloop. As the owner sad, it was on the Oreo upgrade. I'm wondering if its possible to fix it... What you guys say?
Thanks!!
Click to expand...
Click to collapse
Well that depends. If the owner unlock the bootloader and then relocked it it could have screwed it up depending on what he was doing with it at the time resulting in a bootloop that cannot be fixed because it's hard brick now. I say can't be fixed only because the only way to get it fixed as far as I know is to contact someone here on the forums I'm not exactly sure who it is but they do fix hard bricked pixels for money. If I were you I would try and figure out if that's the case before buying it.
Phalanx7621 said:
Well that depends. If the owner unlock the bootloader and then relocked it it could have screwed it up depending on what he was doing with it at the time resulting in a bootloop that cannot be fixed because it's hard brick now. I say can't be fixed only because the only way to get it fixed as far as I know is to contact someone here on the forums I'm not exactly sure who it is but they do fix hard bricked pixels for money. If I were you I would try and figure out if that's the case before buying it.
Click to expand...
Click to collapse
Yes, that's my biggest fear right now... He sad he never had done anything like root or custom rom, he just had done a system update and the phone never boot correctly again.
I have a little bit of knowledge in android, i was thinking if just putting a custom rom it wouldn't solve, because i had other devices that i had put in bootloop and i was able to fix it just putting a custom rom...
rosendomurilo said:
Yes, that's my biggest fear right now... He sad he never had done anything like root or custom rom, he just had done a system update and the phone never boot correctly again.
I have a little bit of knowledge in android, i was thinking if just putting a custom rom it wouldn't solve, because i had other devices that i had put in bootloop and i was able to fix it just putting a custom rom...
Click to expand...
Click to collapse
Can you get to recovery ?
Phalanx7621 said:
Can you get to recovery ?
Click to expand...
Click to collapse
I'm not with the phone right now, I'm going to buy it next week... Correct if I am wrong, but if i can get to recovery or bootloader i can fix it, right?
I think he had tried to unlock the bootloader but without experience had bricked...
rosendomurilo said:
I'm not with the phone right now, I'm going to buy it next week... Correct if I am wrong, but if i can get to recovery or bootloader i can fix it, right?
I think he had tried to unlock the bootloader but without experience had bricked...
Click to expand...
Click to collapse
Yeah if you can get into recovery you can side load things. And if you can get to the boot loader screen you're fine.
Phalanx7621 said:
Yeah if you can get into recovery you can side load things. And if you can get to the boot loader screen you're fine.
Click to expand...
Click to collapse
Perfect! Just as I expected... Probably i will do an youtube guide if it works... Thanks bro!
Hello Everybody,
I had a working Zenfone 2, flashed with LineageOS. I decided to factory reset my phone via the Settings app, as I was intending to pass it off to someone, but instead of taking me to the setup screen, I was brought to TWRP recovery. At this point, when I rebooted to system, it would take me to TWRP again and again. I then decided to wipe everything (dalvik, data, cache, internal storage, etc., except MicroSD, as I was intending to reflash and had the latest LineageOS nightly, GApps, addonSU, and latest TWRP for the Zenfone2).
Within TWRP, I went to install and chose the latest TWRP image to flash to recovery. I then rebooted and it went straight to my bootloader (Fastboot mode). I would show a picture but I am a new user so I cannot. It is the screen with the android laying down with its stomach open. At the top, I can choose between "Normal Boot", "Recovery", "Restart Bootloader", and "Power Off". At the bottom, it says "Fastboot mode", followed by a bunch of information about my device, followed by "Continue the fastboot process?" in green text.
At this point, I can't even get back to the recovery, after using the volume buttons to select to boot into Recovery. It will always bring me back here. Using Fastboot on my computer, I flashed TWRP recovery again, but when the phone reboots, it goes back to the bootloader again, even when I select reboot to Recovery. Since then, I've tried running the Unlock Marshmallow Bootloader file, and my phone said Unlock failed, and I was brought back to the bootloader screen (Except this time, the text at the bottom "continue the fastboot process?" is in blue instead of green). I tried running the Unlock Lollipop bootloader files, and the same thing, my phone said unlock failed, and that is where I stopped because I have absolutely no idea what I'm doing and fear I am just making things worse.
Can anyone help me get my phone functioning again? At this point, I don't care if I have LineageOS on it, or just plain Stock firmware from ASUS. I just want my phone to work again.
Thank you very much in advance.