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

No reason bootloop

Hey guys, let me start off by telling you I was running stock 12b rooted with the 1.5 Furnace kernel. Been running that for 2 weeks solid, no problems. I added 2 Xposed modules last night, swiftkey something and the one to remove the "full battery notification". I rebooted last after enabling them and the phone was fine. Charged phone last night, took it off charger (working fine) and decided to reboot it. Big mistake! It just bootlooped. It would start for 10 seconds, no wifi no data and then restart. I honestly did nothing......
I got into recovery and tried to restore my nandroid backup but same issue. Right now I am flashing 12b from the LG Flash Tool. Will that fix it? Is there another way?
Thanks for all your expertise

Tried to use the LG Flash Tool and it didn't work. Anyone got any ideas how to get my phone to stay working? It boots, for 10 seconds then reboots

If you think it's something to do with xposed why not flash the xposed disabler zip in recovery? Also have you tried a simple wipe of cache and dalvik?
Sent from my LG-D802 using Tapatalk

I finally got the Flash tool to work and got 11a loaded on. So now I am fully stock and unrooted. But, the phone keeps rebooting. Doesn't make any sense. Anyone have any ideas?

tattooz305 said:
I finally got the Flash tool to work and got 11a loaded on. So now I am fully stock and unrooted. But, the phone keeps rebooting. Doesn't make any sense.
you ned to clear cash on stock you can only do that by do a factory hard reset.
https://www.youtube.com/watch?v=3ogBvzbPikc&feature=youtube_gdata_player
Click to expand...
Click to collapse

tumebone said:
tattooz305 said:
I finally got the Flash tool to work and got 11a loaded on. So now I am fully stock and unrooted. But, the phone keeps rebooting. Doesn't make any sense.
you ned to clear cash on stock you can only do that by do a factory hard reset.
https://www.youtube.com/watch?v=3ogBvzbPikc&feature=youtube_gdata_player
Click to expand...
Click to collapse
Thanks for replying. I did a factory reset. Phone boots and hangs on activation for a couple seconds then reboots. Any other ideas?
Click to expand...
Click to collapse

I have a similar problem when restart the phone gets in bootloop. when the phone is operating normally burst without rebooting or any other problems. I'm all factory on it's still 802 10b and does not offer me the option to update the phone. I think it's a software error I have a warranty but I can not wait 30 days to fix my phone
I hope you understand this is a google translate
Sent from my Nexus 7 using Tapatalk

tattooz305 said:
tumebone said:
Thanks for replying. I did a factory reset. Phone boots and hangs on activation for a couple seconds then reboots. Any other ideas?
Click to expand...
Click to collapse
Any luck fixing this? I Have the exact same issue with my ls980(Sprint Variant). I've flashed multiple roms, kernels, and radios with no luck. Used LG Flash tool and it always fails at 94%( when it reboots the phone). However, my phone does say unrooted afterwards. I've also tried wiping all data/ factory reset. No luck.... The phone comes on and doesn't recognize any touch for a long time. Finally, it unlocks, and reboots minutes later. No apps or widgets work. The phone only stays on for so long because I turned on the stay always awake option in developer options. Any help would be greatly appreciated!
Click to expand...
Click to collapse

Unfortunately, I did not find a solution. Amazingly, the only rom that would load was Madallus so that is what I am running. You could try that and see if it will load.

SM910F Note 4 5.1.1 Random Freezes and Restarts

Hello there xda.
I have a Samsung Galaxy Note 4 SM910F.
So what is happening to my phone is that whenever I am in any random app lets say reddit or even chrome for example. It will like freeze for a minute or two and then unfreeze.
In more extreme cases it will reboot.
So this happened randomly because I flashed a Stock unbloated 5.1.1 ROM from here back in december and everything was working smoothly and stuff. I had xposed installed and all my apps. Then in February it started with this random freeze/reboot. I had not installed anything else apart from what I had for the last 3 months.
So I restarted the phone, changed the battery and stuff to see whether that will fix it. However it didn't. So I formatted the phone (the soft type) just so I can install another ROM. So I tried another ROM, flashed the correct CP and BL and stuff and then just installed chrome and whatsapp. After an hour or two the same thing happened. So this time I factory reset he phone, like a complete wipe and I installed the unbloated ROM once again with few apps. Same thing happened...
So my last resort was to install Cyonagen Mod. After an hour or two same thing happened...
I don't know what is the problem. I read about some peoples phones emmc failing and thus the freezing, but I am not sure yet.
Please could you guys explain what I should do to fix this?
Thank in advance!

I have the same problem. Starting on mid january. I'm on stock 5.1.1 with root and twrp recovery
Tried backup and factory reset

I went back to stock after I factory reset the phone. And still had the same problems.
People say that its a hardware problem... So I guess I'll have to send it back to Samsung soon.
I think I tripped the knox. I just have to unroot and get it back once again to stock and send it back. I hope that they accept it.

i have the same problem. my model is SM-N910W8 and I bought it from 2nd hand, so no receipt and no prove of purchase.
can I still send it back to samsung to fix it?

same problem as you and now my phone died completely .
my phone was 4 months and he has not supported any longer he died naturally lol.
my operator gave me another free under warranty because the phone had a faulty motherboard and after several back galaxy note 4

This started happening to me a week or so ago and my phone just got stuck in a boot loop after it froze and rebooted. I'm on the latest stock firmware. Tried factory reset, reflashed stock firmware, nothing helps. It still reboots (sometimes it almost gets booted completely, other times it reboots after 2 seconds.

Just disable finger print. Yes that magic feature offered by Samsung is causing more hungry that happiness since S5

EclipseX said:
Just disable finger print. Yes that magic feature offered by Samsung is causing more hungry that happiness since S5
Click to expand...
Click to collapse
Many thanks. This was driving me mad for a few days, I had tried three different ROMS, completely wiping everything. I eventually went back to stock, which I'm still running and it was the same; it would run fine for a few hours and then start to lock up until eventually it would either reboot or stop responding and I'd have to pull the battery to restart it.
Just not selecting fingerprint security doesn't work, you have to force stop "Fingerprints" in Application Manager (All).

just do not setup the finger print lol. I was having those problemes too when I bought the note 4 until someone tell "do not setup the finger print" lol, not I'm a happy user.... I hope that android 6.0.1 solve the probleme
HXOY said:
Many thanks. This was driving me mad for a few days, I had tried three different ROMS, completely wiping everything. I eventually went back to stock, which I'm still running and it was the same; it would run fine for a few hours and then start to lock up until eventually it would either reboot or stop responding and I'd have to pull the battery to restart it.
Just not selecting fingerprint security doesn't work, you have to force stop "Fingerprints" in Application Manager (All).
Click to expand...
Click to collapse

EclipseX said:
just do not setup the finger print lol. I was having those problemes too when I bought the note 4 until someone tell "do not setup the finger print" lol, not I'm a happy user.... I hope that android 6.0.1 solve the probleme
Click to expand...
Click to collapse
Spoke too soon, it's started rebooting itself again.

Same problems here since 2 days. I was on original 5.1.1 software... Very strange all those people with the same problems

did the problem was resolved ? started to have the same problem 3 days ago ! was on 6- flashed stock with full wipe..nothing ! downgraded to 5.1 with full wipe via odin...again nothing !
WTF [email protected]!

Davids said:
did the problem was resolved ? started to have the same problem 3 days ago ! was on 6- flashed stock with full wipe..nothing ! downgraded to 5.1 with full wipe via odin...again nothing !
WTF [email protected]!
Click to expand...
Click to collapse
Still having the same issue around the same time everyone else started experiencing it.
I also was rooted and had xposed installed on 4.4.4 before the issue started happening.

Try the solution provided here & report back..
http://forum.xda-developers.com/note-4/help/note-4-sm-n910f-freeze-restart-issue-t3439111

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!

Anybody else have a main board failure? Here is my story.

Last week I was minding my own business, doing usual stuff on my phone and the device spontaneously rebooted into a bootloop at the Google logo. So I think "OK, no problem... I can try wiping cache/dalvik or at worst I have a recent nandroid backup" and proceed to reboot into recovery... except that it still hangs on the Google logo. Stuck at work I did a bunch of googling and found one other user who had the same thing happen recently.
When I got home I tried to fastboot flash TWRP again... but alas was still stuck at the Google logo. Next was a full flash of Google stock images, but that did nothing either... so I relocked the bootloader and had my provider (TELUS) send it in for warranty repair. I just had it returned with the repair stating the main board was replaced.
I have noticed a few users posting about being stuck on the Google logo and this concerns me a bit, as it almost seems like there may be some inherent hardware flaw causing the issue.
So I'm throwing the questions out there: Has anyone else had similar problems and is this something we should start to be concerned with?

You're not alone buddy. I'm in the same boat. Have sent mine for repair yesterday.

Thats discouraging news. How long have you guys owned the phone? Did you buy it new?
I love my 6p but if enough of these units are defective they should probably be recalled. Hard to gauge if its an anomaly or a serious issue. Hope for the former...

I think I may have the same problem. My phone wont boot past the logo at all. IDK what to do at all.

I have the same problem, stuck on the google logo, I already wiped the cache partition and nothing, did a factory reset and nothing, what else can I do??

KLit75 said:
Thats discouraging news. How long have you guys owned the phone? Did you buy it new?
I love my 6p but if enough of these units are defective they should probably be recalled. Hard to gauge if its an anomaly or a serious issue. Hope for the former...
Click to expand...
Click to collapse
7 months...
Sent from my Nexus 4 using Tapatalk
---------- Post added at 09:51 AM ---------- Previous post was at 09:48 AM ----------
hgil said:
I have the same problem, stuck on the google logo, I already wiped the cache partition and nothing, did a factory reset and nothing, what else can I do??
Click to expand...
Click to collapse
Check if you can boot twrp. If you're not successful send the phone for repair. No option available to recover from this king of hard brick yet.
Weird thing is anything and everything is doable in fastboot. Moment you try to boot OS or recovery, gets stuck indefinitely in Google logo and reboot.
Sent from my Nexus 4 using Tapatalk

this exact thing literally just happened to me on Thursday. I was fully stock never unlocked the bootloader or anything. phone suddenly started looping, tried wiping cache, doing factory reset, finally went nuclear and unlocked the bootloader and flashed system images. nothing worked. warranty replacement is enroute.
I bought it on release day.

Old issue with Nexus devices. Has been going on since Nexus 5
Sent from my ONEPLUS A3000 using XDA-Developers mobile app

I got the phone new from TELUS at the end of December, so about 6mo before I had the issue... Thankfully fastboot still worked so I could return to stock and relock the bootloader before warranty claim...
Starting to wish I had done the insurance option if these things are failing after 6mo and I'm on a 2yr contract

sunseb said:
I got the phone new from TELUS at the end of December, so about 6mo before I had the issue... Thankfully fastboot still worked so I could return to stock and relock the bootloader before warranty claim...
Starting to wish I had done the insurance option if these things are failing after 6mo and I'm on a 2yr contract
Click to expand...
Click to collapse
Did they give a new/refurb or was it they changed motherboard/memory chip?
Sent from my Nexus 4 using Tapatalk

Was my original exterior, the dings were still on the corners so it was just motherboard replacement

sunseb said:
Was my original exterior, the dings were still on the corners so it was just motherboard replacement
Click to expand...
Click to collapse
Thanks. Just was curious on what I could expect.
Sent from my Nexus 4 using Tapatalk

I'm also having this issue, but I get stuck at the boot animation instead.
I have Nexus 6P, Stock Android 6.0.1 July, SuperSu v2.74, franco kernel r23, Xposed v85. Everything was running fine when suddenly the phone rebooted and got stuck in boot. I reboot into recovery, deleted the /data/data/de.robv.android.xposed.installer/conf/modules.xml, flashed xposed unistaller zip, cleared cache and rebooted. Still stuck in boot. I reboot into bootloader, flash boot, system, vendor image of July factory image and reboot. Still get stuck at boot. This is happening for the third time to me. Happened in May, in June and now in July. Only thing that works is restoring a nandroid and then again flashing the latest factory image. But that way, I lose days / weeks of data, depending on when that last nandroid was created.

That really sucks, but doesn't sound like a hardware failure from my understanding... I lost ALL my data when I had to send it in, since my failure resulted in no access to the internal memory... Lost a few pictures which was a real bummer, but lesson learned and now I'll be backing up my memory more frequently and also setting up cloud backup for photos

bagarwa said:
I'm also having this issue, but I get stuck at the boot animation instead.
I have Nexus 6P, Stock Android 6.0.1 July, SuperSu v2.74, franco kernel r23, Xposed v85. Everything was running fine when suddenly the phone rebooted and got stuck in boot. I reboot into recovery, deleted the /data/data/de.robv.android.xposed.installer/conf/modules.xml, flashed xposed unistaller zip, cleared cache and rebooted. Still stuck in boot. I reboot into bootloader, flash boot, system, vendor image of July factory image and reboot. Still get stuck at boot. This is happening for the third time to me. Happened in May, in June and now in July. Only thing that works is restoring a nandroid and then again flashing the latest factory image. But that way, I lose days / weeks of data, depending on when that last nandroid was created.
Click to expand...
Click to collapse
It's likely a software failure. When you flash via fastboot, do you reboot back to bootloader after flashing radio and bootloader? If not then that's likely what's causing the fast boot method to fail for you. The first time after I did a complete fastboot flash of the software I fell asleep and woke up in the morning to my 6p still at the boot screen. When I re-traced my steps I found out that my mistake was not properly rebooting after flashing radio image, then doing another reboot after flashing bootloader.

Got my device back. Same exterior. Was told that motherboard was changed. I could notice that from fastboot.
eMMC changed from Samsung to Toshiba
DRAM changed from Hynix to Samsung.

My device joins this list. Gonna send it for repair tomorrow and hoping it is covered under warranty.

Additional update. I know I missed the bigger scheme that changed. My IMEI.
Just curious what happens if I restore my previous efs partition backup after backing up current.
Sent from my Nexus 6P using Tapatalk

update: My phone came back in 5 days. Mainboard failure. Replaced in Warranty!! New IMEI!!
Sent from my AO5510 using Tapatalk

sunseb said:
Last week I was minding my own business, doing usual stuff on my phone and the device spontaneously rebooted into a bootloop at the Google logo. So I think "OK, no problem... I can try wiping cache/dalvik or at worst I have a recent nandroid backup" and proceed to reboot into recovery... except that it still hangs on the Google logo. Stuck at work I did a bunch of googling and found one other user who had the same thing happen recently.
When I got home I tried to fastboot flash TWRP again... but alas was still stuck at the Google logo. Next was a full flash of Google stock images, but that did nothing either... so I relocked the bootloader and had my provider (TELUS) send it in for warranty repair. I just had it returned with the repair stating the main board was replaced.
I have noticed a few users posting about being stuck on the Google logo and this concerns me a bit, as it almost seems like there may be some inherent hardware flaw causing the issue.
So I'm throwing the questions out there: Has anyone else had similar problems and is this something we should start to be concerned with?
Click to expand...
Click to collapse
my phone randomly locked up, then rebooted today. But when it rebooted it was stuck with the white google logo flashing. I can get into the bootloader mode, but from there, choosing recovery or anything else gets back into the white google bootloop. I called service and they're sending me a replacement. Phone was stock with a locked bootloader.