Database Users

Nexus 4 TWRP encryption with password - I think the phone is gone

So, I have read a lot about TWRP sometimes bugging out and randomly encrypting phones and adding a password to which the user either never set it up or that TWRP doesn't accept it. This has recently happened to me and I cannot use my phone and I don't know what to do.
I have had the bootloader of my phone unlocked since day 1 when I bought my phone (release date last year) and have been running PA ever since. I have never had any problems with it, until about 5 days ago, when I grabbed my phone and everything started crashing and the camera was apparently not available. I didn't know what was the deal with it, so I rebooted the phone and it entered a bootloop (it hangs on the Google logo for about 5 minutes and then it hangs on the PA logo screen forever). I went on to the bootloader and started TWRP to see what was the deal. I originally wanted to grab certain files off the phone in case I had to do a system format, but when I got to TWRP, it asked me for a password which I have never set up and I tried every combination I could think of but it always failed. Everything was encrypted and without the password I couldn't get to it. I tried wiping everything including a factory reset before resorting to a system format (which I read about it and apparently is meant to be the solution). Everything failed because it couldn't access the /cache, /data, nothing. I went on to do a system format and although that is meant to wipe the phone and remove encryptions, it also failed to wipe the /cache and although TWRP says that the wipe is successful, the phone is still encrypted, the password is still around and it bootloops. I have tried the system format like 50 times and always the same.
Can anyone help me out with this? I am currently travelling around but am at a hostel where there is great internet and pcs, so I can install drivers, toolkits and such. I actually started looking around for new phones, since I cannot for the life of me get the phone to start again.
Note: The phone was working perfectly fine, I put it down to have dinner and once I finished, I tried to use it and it started to bug out. I also read around about this, and everyone's issue gets fixed after a system format.
Any help, would be greatly appreciated, that phone is the only net device I have on this trip and it sucks to not have any way to contact anyone.
Thanks.

Bump

Don't blame TWRP for something it doesn't do.
Looks like your device have an EMMC failure, sorry.
You can try installing factory image, or last resort restoring by download mode, but I think the flash memory in your phone is gone.
http://forum.xda-developers.com/showthread.php?t=2347060
sent from nexus 4

eksasol said:
Don't blame TWRP for something it doesn't do.
Looks like your device have an EMMC failure, sorry.
You can try installing factory image, or last resort restoring by download mode, but I think the flash memory in your phone is gone.
http://forum.xda-developers.com/showthread.php?t=2347060
sent from nexus 4
Click to expand...
Click to collapse
I didn't mean to blame TWRP. It is just that it was when I am on it that I get asked for the password and I was under the impression that it was TWRP that did the encrypting (I am in no way a developer or even very knowledgeable when it comes to the under the hood stuff, I usually only follow the tutorials). But thanks for the reply and the link, I will try that and hopefully get the phone back working.
Also, I did read in a thread that apparently this can occur due to hardware failure, I was just hoping this wasn't the case.

This happened to me on an old phone. Not sure why. Factory image fixed it. Could be a different issue but its worth a shot.
Sent from my Nexus 4 using XDA Premium 4 mobile app

It's happening to me now too
Sent using T-Mobile S4 4.3 MK2

LEGEND94 said:
It's happening to me now too
Sent using T-Mobile S4 4.3 MK2
Click to expand...
Click to collapse
Did it suddenly happen or did you change ROMs?

I tried a new rom for the first time and then went back to wicked 9.1, I'm thinking that triggered something.
I think I got a fix though, look here: http://forum.xda-developers.com/showthread.php?t=2588377
Sent using T-Mobile S4 4.3 MK2

[Q] Nexus 4 updated to Kit Kat via OTA and got looped on boot

Hi, this is my first post here. I'm new into Android and I've always updated my Nexus 4 when the system prompts me to do it. Today, I got the notification to update from 4.3 to 4.4... I did it and restarted my phone. Then I got (and have been) stuck on the boot sequence after the Google logo. The thing is that I've tried to wipe and restart the phone by Bootloader (I don't know if I lost all of my files) and didn't work out. So now I'm trying with Nexus Root Toolkit but I don't know if that will work. I'm really needing some help, here in Venezuela not so many people have this cellphone and I really don't know how to proceed. I'm upset with Google for these kind of fails, my phone was working 100% good. Please help me! Sorry if my english is not so perfect.

I did experience the same.
Never rooted or unlocked bootloader & I was patiently waiting for OTA. It came and it was the worst thing to happen! Infinite bootloop!
I waited 2 hours, before I restarted the phone, but in vain. No use!
I never enabled debug settings, so i couldn't use ADB command and it wasn't recognizing my device!
Here is what worked for me:
1. Unlock bootloader (using fastboot command)
2. use fastboot to flash the factory image
3. I did remove (-w) wipe option, but still lost my data.
however image works, now phone is back to life!

Same case, nothing works.

I had the same problem, go stuck on a boot loop and then it just said 'no command' or 'error' with an android lying down. Im a noob so i used ncry toolkit to reset it to factory 4.3 and then i upgraded to 4.4 again and all worked fine. Did lose data though, but i had it all backed up.

Do a clean flash of KitKat via fastboot.

Similar Situation
Chidvilas said:
I did experience the same.
Never rooted or unlocked bootloader & I was patiently waiting for OTA. It came and it was the worst thing to happen! Infinite bootloop!
I waited 2 hours, before I restarted the phone, but in vain. No use!
I never enabled debug settings, so i couldn't use ADB command and it wasn't recognizing my device!
Here is what worked for me:
1. Unlock bootloader (using fastboot command)
2. use fastboot to flash the factory image
3. I did remove (-w) wipe option, but still lost my data.
however image works, now phone is back to life!
Click to expand...
Click to collapse
I'm in the same situation as most... Sadly I updated via the OTA distro that was released a few days ago. I looked into rooting options and I got the "go ahead" from a thread somewhere, saying it is a minor update. Knowing how easy it was to restore root priveliges when I upgraded from 4.2 to 4.3, I trusted their encouragement and installed the update. Then, like everyone else, I got stuck in the bootloop at the "circles" screen.
As a last resort, I tried to factory reset to no avail. I cleared the dalvik cache and wiped the cache partition a few times... Then I tried restoring it to factory defaults, again! Same results every time. Unfortunately, because of where it gets hung up, I can't seem to get my computer to talk to it. I certainly can't access the SD Card to do any backing up, but can look at the contents through CWM recovery mode (v6.0.2.3).
It's been awhile since I last was active in flashing my phone, so while I no longer consider myself a noob, I am definitely back to being a beginner. The fastboot commands don't seem to work, as I get stuck at "<waiting for device>". Does anyone know if there is a way to force it into a drive mode? Any additional help with this matter would be greatly appreciated, as currently it seems Google has bricked my phone!
Last question, it looks like it may be possible to force a mount through CWM; is that true using the "mounts and storage" menu? I spoke to Google briefly and they were of no help (they just told me to call LG). I'm going to try going into the T-Mobile store and seeing what they will say, but I'm not holding my breath for them to come up with a solution; I'm relying on the community to help me out!
STATS:
Bootloader: MAKOZ20i
HW Version: rev_11
Secure Boot: enabled
Lock State: unlocked
CWM: v6.0.2.3
Computer OS: Linux-Ubuntu 13.4
---------- Post added at 03:48 PM ---------- Previous post was at 03:39 PM ----------
NissanskylineN1 said:
Do a clean flash of KitKat via fastboot.
Click to expand...
Click to collapse
Sorry to sound so dumb, but can you point me in the right direction to find instructions on how to do that with Linux?

http://forum.xda-developers.com/showthread.php?t=2302780
Its actually way easier to set it up on Linux than on windows.
Edit: java jdk6 was giving me issues on install so I used openjdk instead and it works perfect.
Edit: (last one, I promise), I don't know how new you are to Linux but if you are super new, anytime that guide mentions "code" in a box, copy and paste one line at a time into the terminal. Leave out the dollar signs when copying.
AMarted said:
I'm in the same situation as most... Sadly I updated via the OTA distro that was released a few days ago. I looked into rooting options and I got the "go ahead" from a thread somewhere, saying it is a minor update. Knowing how easy it was to restore root priveliges when I upgraded from 4.2 to 4.3, I trusted their encouragement and installed the update. Then, like everyone else, I got stuck in the bootloop at the "circles" screen.
As a last resort, I tried to factory reset to no avail. I cleared the dalvik cache and wiped the cache partition a few times... Then I tried restoring it to factory defaults, again! Same results every time. Unfortunately, because of where it gets hung up, I can't seem to get my computer to talk to it. I certainly can't access the SD Card to do any backing up, but can look at the contents through CWM recovery mode (v6.0.2.3).
It's been awhile since I last was active in flashing my phone, so while I no longer consider myself a noob, I am definitely back to being a beginner. The fastboot commands don't seem to work, as I get stuck at "<waiting for device>". Does anyone know if there is a way to force it into a drive mode? Any additional help with this matter would be greatly appreciated, as currently it seems Google has bricked my phone!
Last question, it looks like it may be possible to force a mount through CWM; is that true using the "mounts and storage" menu? I spoke to Google briefly and they were of no help (they just told me to call LG). I'm going to try going into the T-Mobile store and seeing what they will say, but I'm not holding my breath for them to come up with a solution; I'm relying on the community to help me out!
STATS:
Bootloader: MAKOZ20i
HW Version: rev_11
Secure Boot: enabled
Lock State: unlocked
CWM: v6.0.2.3
Computer OS: Linux-Ubuntu 13.4
---------- Post added at 03:48 PM ---------- Previous post was at 03:39 PM ----------
Sorry to sound so dumb, but can you point me in the right direction to find instructions on how to do that with Linux?
Click to expand...
Click to collapse

Massive softbrick (haven't found a solution yet)

Hello everyone,
So here's my story: I got a 6P short after release and it's been amazing. After switching from a S6 I couldn't be happier until 3 days ago.
I was playing around with my phone (checking for updates on the play store if I recall correctly) and I was going to switch from 4g to wifi. I went ahead and pulled down my notification shade and went to press WiFi but misclicked and hit Hotspot which was below it. My phone suddenly froze big time and this is for the first time ever since purchase.
At first I thought I'd wait it out since the device was completely unresponsive, home button didn't work and neither did anything on screen. Buttons didn't make a difference either. 10 minutes went by and I ended up force restarting by holding down power + volume up. First part of my bootup went fine but when it got to the android boot animation after I put in my pin to allow the device to start it dropped from the smooth usual framerate down to 1 frame every 10-15 seconds and it slowed down further until it came to a complete halt around the time the android letters appear.
My first thought was corrupt rom so I went ahead and wiped data from the stock recovery. I was running completely stock with no modifications whatsoever. That didn't do anything. Phone still froze in the same boot phase. Desperate I unlocked bootloader to flash a clean fresh image to try to fix it and to my surprise that didn't change a thing.
As I was getting pretty desperate already I had one more idea and that was to flash up to the Dev preview. To my huge surprise it booted and I jumped from excitement. So I started setting up my phone again. I got past the prompt to insert sim card and I was now at the screen to choose a wifi network. As soon as I clicked into that the phone froze up again and at that point I lost all hope.
I wiped data in stock recovery and shut the phone down for the night. On day 3, today I woke up and tried starting the phone and it worked as if nothing had happened. I went through the setup and set up my phone on the N preview. At a certain point I was planning to go back to the latest official build but for now I was happy my phone was back from the dead. Later today I tried to restart my phone to clear all running apps etc and it froze up on boot.
I'm losing all hope that I'll be resolving this myself so I'm reaching out to the community to see if anyone's had this happen to them before and hopefuly for a solution. It's still under warranty so I can eventually send it back to the retailer but I'd rather not have a phone for 3 weeks.
Any and all help is appreciated.
Thank you for reading through my long and probably pretty boring story!

Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?

To the OP, is there any reason you did not flash to release version 6 instead of Dev preview ?
Also, any reason you can not simply do the "unenroll" from https://www.google.com/android/beta ?
It will require you to setup certain settings again as you will be back to a "factory reset".

DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
DJBhardwaj, i haven't specifically erased those partitions. I was under the impression wipe userdata along with reflashing did that. I will try that tonight when I get home!
Xdafly, I only updated up to N as a last resort because at first I had a locked BL. I was planning to unenrol but that would've been too late as it self bricked after a restart.

DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
Well I just did the erase thingy and my phone booted but wifi won't turn on. Enabling hotspot doesn't brick anymore but I now suspect WiFi might've been the issue. Any tips on how to find out what it could be and possibly fix it?
Edit: 2 restarts and a factory reset later I'm back to bricked same way as before.

try safe mode

mr.dj26 said:
try safe mode
Click to expand...
Click to collapse
That was my first thought, that was the restart that bricked it again. Safe mode shouldn't have made a difference since I hadn't even logged into Google account for apps.

After reading the very first post; sounds like bad WiFi hardware.
All the hanging has been related to WiFi or Hotspot.

I think you should get a replacement
Sent from my Purified NexusixP
If Someone Helped You Then Dont Just say Thanks...Hit The Thanks Button!

Is your phone rooted and did you install Xposed?
Over the weekend I shutdown my 6p (stock rooted with April security patch, Xposed v80) and charged it. When it turned it back up I kept getting "Unfortunately, nfc service has stopped". Long story short: I ended up factory reset my phone and reinstalled EVERYTHING and I still got into bootloop. Then I came across
https://github.com/rovo89/Xposed/issues/113
https://github.com/rovo89/android_art/issues/28
At the end of the second post rovo89 (developer of Xposed) fixed the bug in V83. I wiped my 6p once more and installed everything with v83. Problem solved.
Good luck!

Phone restarts at startup.

Well this is my 1st post so first of all hey everyone
I just spent a week in Amsterdam and my phone restarted twice, different times different days and I dont remember what I was doing with it back then.
But as I landed back home I put the phone back from "Airplane Mode" and went on to toggle "Cellular Data" on.
The second I pressed the cellular data shortcut on my the phone restarted itself but this time whenever it would finish the screen would be on but fully black and sometimes it'll show battery precentage at the top but then will restart again in an infinite loop.
Sometimes it'll pop up the "Optimizing Apps" window and will go through all 24, upon finishing it will restart once more and do the same.
I tried using the bootloader and it worked (the bootloader that is) but the phone would do the same thing even after Rebooting from there or shutting down from there and then turning back on.
I contacted tech support on chat but they couldnt help past telling me to go to bootloader and reboot, said I should factory wipe when it failed.
Also tried wiping cache but to no avail.
I have no backup of my phone (wanted to do one before the flight but got lazy and I suck for not doing one sooner) since probably October and google doesnt backup my contacts properly for some unknown reason.
I already downloaded Android Studio with everything included for me to try using adb to sideload stock without wiping but its my first time and I couldnt get it to do anything at all...
I already got the official stock .gz file from the motorola website.
Anyway here are the specs to my phone:
XT1575
Everything is stock. didn't root or change recovery once in my life.
Was fully updated and had plenty of drive space (I have almost 128GB with the 64GB version + 64GB SD)
I'm really lost here so help will be very appreciated.
Thanks in advance,
-Noam

Start with a full wipe and if that doesn't work flash the stock image. Not sure what your question is though as you never really say. Once fixed I would unlock and make a backup so you don't have to deal with this again.

lafester said:
Start with a full wipe and if that doesn't work flash the stock image. Not sure what your question is though as you never really say. Once fixed I would unlock and make a backup so you don't have to deal with this again.
Click to expand...
Click to collapse
The thing I pretty much want to know is if theres a way to either backup the phone now with it connected to the computer while in bootloader or recovery. or a way to flash the stock rom without wiping which I read someone did with his tablet. I cant post source normally because I'm a new user so here it is but change spaces to dots: schnouki net/posts/2014/08/13/flashing-a-stock-android-image-without-wiping-user-data/
Also while in recovery I noticed 2 options under wipe: 1. userdata only. 2. userdata+(insert something I dont remember here) and I was wondering what gets deleted in both? if I delete only userdata what data will remain? something helpful?

Sure you can try flashing without wiping data but being locked I personally wouldn't risk it. No idea about backing up in your state... somewhere I remember a thread on backing up without root try searching in q&a.

lafester said:
Sure you can try flashing without wiping data but being locked I personally wouldn't risk it. No idea about backing up in your state... somewhere I remember a thread on backing up without root try searching in q&a.
Click to expand...
Click to collapse
Out of curiosity why shouldnt I try flashing with no wipe if ill lose the data anyway? worst case wont I just have to wipe after it fails and flash again?
And I will try thank you
Do you have any knowledge about the 2 wipe options?
Thanks in advance

Well I tried turning the phone on and it took a couple of minutes before loading to a fresh start. It apparently wiped itself on its own. Managed to restore almost everything.
Anyhow the phone takes too long to boot now. Was even stuck at boot and I had to restart it.
Anyway to fix my software? Or at least check for corruption?
Sent from my XT1575 using XDA-Developers mobile app

"Decryption unsuccessful" message on stock 7.0/7.1.1

This is the second time I get this message. First time was on stock Android 7.0. next time, ~2 weeks later on stock Android 7.1.1. To revive my phone I had to perform a factory reset twice.
What causes this message? Is it software or hardware related? I assumed the former, but the fact that it happened twice after a reset and on a new version made me wonder...
I'm heading to a country without 3G coverage and barely any WiFi, so if this happens then, I'm screwed on 2 levels: -Loss of pictures, due to not able to back-up -Not able to reset, since that requires WiFi.
Anyone else who had this issue? Any recommendations, RMA?
Full error message: "Decryption unsuccessful" The password that 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"
Thx.

You can set the phone to back up without wifi if you are good with that I've had my phone since December I have not had that happen odd.
Sent from my Nexus 6P using Tapatalk

gjkrisa said:
You can set the phone to back up without wifi if you are good with that I've had my phone since December I have not had that happen odd.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
And how would you do that? Can't seem to find any way to do that...

In Google photos there is in settings also drive after that I believe the rest of settings will back up w/o wifi I know photos will
Sent from my Nexus 6P using Tapatalk

Dytoonn said:
This is the second time I get this message. First time was on stock Android 7.0. next time, ~2 weeks later on stock Android 7.1.1. To revive my phone I had to perform a factory reset twice.
What causes this message? Is it software or hardware related? I assumed the former, but the fact that it happened twice after a reset and on a new version made me wonder...
I'm heading to a country without 3G coverage and barely any WiFi, so if this happens then, I'm screwed on 2 levels: -Loss of pictures, due to not able to back-up -Not able to reset, since that requires WiFi.
Anyone else who had this issue? Any recommendations, RMA?
Full error message: "Decryption unsuccessful" The password that 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"
Thx.
Click to expand...
Click to collapse
Did you experience any random reboots?
When you say stock you confirm that it's full stock (no root and running google's kernel) ?

rchtk said:
Did you experience any random reboots?
When you say stock you confirm that it's full stock (no root and running google's kernel) ?
Click to expand...
Click to collapse
Never had any troubles with random reboots.
My phone froze, got unresponsive. I had to restart, and when it tried to boot I got this message. This happened twice.
No root, standard kernel. Bootloader not even unlocked.

Dytoonn said:
Never had any troubles with random reboots.
My phone froze, got unresponsive. I had to restart, and when it tried to boot I got this message. This happened twice.
No root, standard kernel. Bootloader not even unlocked.
Click to expand...
Click to collapse
That's it. Storage corruption and the decryption unsuccessful is a consequence of your problem.
Sorry but that looks like a defective device.
ram/emmc/power, it's hard to find without root/twrp. Unless an update got wrong but I don't think that would show these symptoms.
First, I would also raise a PR on google to see what they suggest: https://source.android.com/source/report-bugs.html
You really need to backup your data and have a backup phone in case the following gets you a brick..
I'd actually try flashing factory images (you won't be able to flash recovery image but others yes ). Make sure to record the messages returned on your PC to see if something went wrong. The update process is a bit dumb, it goes on even if errors are encountered so even if it finishes it doesn't mean much.
Once the device is flashed, if it boots, you could try filling your data partition by moving big files using usb transfer. When its full, reboot and see what's happening.
If you are short on time, prepare the RMA process...
edit: oh btw, I'm sure people would be interested to get the information displayed in bootloader mode (power on the phone by pressing volume down)

rchtk said:
That's it. Storage corruption and the decryption unsuccessful is a consequence of your problem.
Sorry but that looks like a defective device.
ram/emmc/power, it's hard to find without root/twrp. Unless an update got wrong but I don't think that would show these symptoms.
First, I would also raise a PR on google to see what they suggest: https://source.android.com/source/report-bugs.html
You really need to backup your data and have a backup phone in case the following gets you a brick..
I'd actually try flashing factory images (you won't be able to flash recovery image but others yes ). Make sure to record the messages returned on your PC to see if something went wrong. The update process is a bit dumb, it goes on even if errors are encountered so even if it finishes it doesn't mean much.
Once the device is flashed, if it boots, you could try filling your data partition by moving big files using usb transfer. When its full, reboot and see what's happening.
If you are short on time, prepare the RMA process...
edit: oh btw, I'm sure people would be interested to get the information displayed in bootloader mode (power on the phone by pressing volume down)
Click to expand...
Click to collapse
Thanks for your reply.
I sent it for an RMA, so unfortunately not able to do what you described. Couldn't chance it getting this error message when abroad.
Curious though if they will grant an RMA, nothing much is looking wrong at the moment. Hope they will, because else I'm screwed.
If they don't, though, I'll see if I can get the information displayed in bootloader mode.

I'm having the same issue.
Same message, only I'm BL unlocked, rooted and twrp.
It happened twice. Once on 7.1 DP1, and again on DP2.
Once I get into recovery, the system is encrypted, and I can't do a thing.
I'm going to try and back up to a flash drive, and try to mount that in twrp if it happens again.

rwj5279955 said:
I'm having the same issue.
Same message, only I'm BL unlocked, rooted and twrp.
It happened twice. Once on 7.1 DP1, and again on DP2.
Once I get into recovery, the system is encrypted, and I can't do a thing.
I'm going to try and back up to a flash drive, and try to mount that in twrp if it happens again.
Click to expand...
Click to collapse
Recent Twrp now supports full disk encryption so you should be able to see your files? And even do a backup from there. Take twrp 3.0.2-3

rchtk said:
Recent Twrp now supports full disk encryption so you should be able to see your files? And even do a backup from there. Take twrp 3.0.2-3
Click to expand...
Click to collapse
Strange, that's exactly the version I'm using.

rwj5279955 said:
Strange, that's exactly the version I'm using.
Click to expand...
Click to collapse
Weird. I don't have twrp so I can't check but you should see your data. Maybe the partition needs to be mounted (I think it is by default though). No /data/media ? /sdcard is the same but as a virtualized FAT file system to be able to be access from Windows. Could be that /sdcard is empty in twrp but /data/media shouldn't.

rchtk said:
Weird. I don't have twrp so I can't check but you should see your data. Maybe the partition needs to be mounted (I think it is by default though). No /data/media ? /sdcard is the same but as a virtualized FAT file system to be able to be access from Windows. Could be that /sdcard is empty in twrp but /data/media shouldn't.
Click to expand...
Click to collapse
I'll have to look if it happens again.
I only remember trying to access /sdcard. Empty

https://twrp.me/faq/datamedia.html

Same issue , rooted and twrp noto e4 plus , any help ? Idk what's is going on

Joeykatie said:
Same issue , rooted and twrp noto e4 plus , any help ? Idk what's is going on
Click to expand...
Click to collapse
If I understand this thread flash custom kernel like ElementalX to unencrypt your device.