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] N7 4.4 update issues?

Not sure if I'm the only one, and if I am that really sucks, but I got tired of waiting for the OTA and decided to install the update via the fastboot method, unlocked my bootloader installed without a problem.
However the issue now seems to stem from transferring media files to my tablet, which I never had a problem doing, a pop up window will tell me that android.media.storage has stopped, giving me an option to report and to simply tap okay.
Not sure reporting ever does anything, and if it does I've never seen it change a single thing at all, but after I tap okay or send the report, any files transferring will just exit out, then if I unplug my usb and plug it back in, it doesn't seem to recognize the tablet at all.
I've so far remedied this, not sure if it's a permanent fix or temporary, by going into settings>apps>all, then from there tapping the app, clearing data and cache, restarting my tablet with a hard reset and it seems to be working for the moment.
However transferring files since the update are sluggish at best, and taking a 356MB folder of images used to take maybe a few minutes, 5 or 7 at the most, now it's hanging there at times with the transfer time increasing.
As a matter of fact I'm transferring said 356MB folder right now and it's stuck at 10 minutes to finish and hasn't moved for about 10 minutes.
If anybody else is having these problems, can you suggest ways you've fixed it? Or do I simply need to either do a factory reset or straight up flash it again to fix the problem?
Also, I made another article detailing my problems with updating, which I've since fixed obviously, but Recovery Mode isn't anywhere to be found, I do the regular method and before it showed the android with the red triangle and below him it would say no command, now it just shows the android with the same triangle with no wording underneath at all.
I've also re-downloaded the official factory image 4.4 from google's developer site and tried to manually flash recovery onto it, and it says that it succeeded but then when it goes back to fastboot and I choose recovery it loads then shows me the android with the red triangle.
I've even tried downgrading back to 4.3 but it tells me during the rewrite of the bootloader that there's a signature mismatch.
In addition, this should be the last revision to my issue, I've even tried re-flashing 4.4 and now that's kicking back an error saying there's a signature mismatch, so I can't go into recovery, I can't downgrade, I can't flash a recovery image to my tablet, I think I screwed up in ever updating to 4.4.

Im having the same problem with Media Storage when transferring pictures via Android File Transfer on Mac, tried it on Windows also, same problem.
It happens with my Nexus 4 on KitKat also!!
I still havent found a way to fix it, did you (OP) ever find a fix?
Cheers
Stewart

StuMcBill said:
Im having the same problem with Media Storage when transferring pictures via Android File Transfer on Mac, tried it on Windows also, same problem.
It happens with my Nexus 4 on KitKat also!!
I still havent found a way to fix it, did you (OP) ever find a fix?
Cheers
Stewart
Click to expand...
Click to collapse
Nope no fix yet, I haven't tried transferring a large number of files since, oddly enough, I finally did get the OTA update and it installed 4.4 again.
It didn't take long and the file size was puny, only about 32MB, I assume it installed what was missing, but I haven't noticed anything out of the ordinary since the official updated kicked in.

Yeah I have the latest OTA also, but I am still having the same issue!!

StuMcBill said:
Yeah I have the latest OTA also, but I am still having the same issue!!
Click to expand...
Click to collapse
Not really sure why it's different for you, like I said I got tired of waiting for the OTA and manually flashed the factory image, that's when the problems started, but after a few days I got a notification that the new update was ready which really confused me.
But I installed the downloaded update without a hitch, booted like normal and I just finished transferring a 100MB folder of images to my N7 without an error popping up on my tablet saying something crashed, so I can only assume for the moment until I transfer a larger folder, that the DL'd update fixed the problem.
I've also heard people flashing it again, or side loading it, or even a factory reset would fix the problem, but there weren't many replies as to this actually fixing the data transfer problem.

Problem with downloading ota update kitkat 4.4
I have stock rom and waited for the ota update. It came this morning and while downloading twice the verification failed.i rebooted and the screen came up download failed and had a retry button which i tried to activate and does nothing, The screen has been stuck on the return download for over 12 hours. My wifi connection is strong. Any ideas?

manow91 said:
I have stock rom and waited for the ota update. It came this morning and while downloading twice the verification failed.i rebooted and the screen came up download failed and had a retry button which i tried to activate and does nothing, The screen has been stuck on the return download for over 12 hours. My wifi connection is strong. Any ideas?
Click to expand...
Click to collapse
Take anything I say with a grain of salt as I'm not the greatest guy to ask for help, I only really ask questions here and I'm just going to suggest what to do, if you do it is up to you and I take no responsibility for your device having further issues.
1. Hard reset your device and upon it rebooting, check for the update again and try downloading it again
2. If that doesn't work then back up your data
3. After backing up your data do a factory reset on your device and once you've booted back up to Android, check for the update again and install
4. If that doesn't work, I'm not sure what else to suggest, this is what I would do to try and fix the problem, but for my situation it was unique in that I tried fixing it various ways that seemed to make it worse before it got somehow better.
I hope issuing a factory reset works for you, if not then that hard reset does when you try to redownload the update.

JohnathanKatz said:
Take anything I say with a grain of salt as I'm not the greatest guy to ask for help, I only really ask questions here and I'm just going to suggest what to do, if you do it is up to you and I take no responsibility for your device having further issues.
1. Hard reset your device and upon it rebooting, check for the update again and try downloading it again
2. If that doesn't work then back up your data
3. After backing up your data do a factory reset on your device and once you've booted back up to Android, check for the update again and install
4. If that doesn't work, I'm not sure what else to suggest, this is what I would do to try and fix the problem, but for my situation it was unique in that I tried fixing it various ways that seemed to make it worse before it got somehow better.
I hope issuing a factory reset works for you, if not then that hard reset does when you try to redownload the update.
Click to expand...
Click to collapse
Thanks for your reply back. Yep i also thought of the same 4 step solution as yourself but i also heard from 2 people that had the same thing happen to them and they thought it could be a goggle server problem, So i am going to wait to see if it sorts itself out over the next few days

manow91 said:
Thanks for your reply back. Yep i also thought of the same 4 step solution as yourself but i also heard from 2 people that had the same thing happen to them and they thought it could be a goggle server problem, So i am going to wait to see if it sorts itself out over the next few days
Click to expand...
Click to collapse
That could be too, just thought I'd take a shot, hope it works out for you.:good:

Is my XT1575 recoverable?

My XT1575 just decided to go into a bootloop a week ago on its own, literally. I was just checking traffic on Google maps when I noticed it started to lock up. Finally, I see the Motorola splash screen, and that was the beginning of it. Went into recovery mode and tried a factory reset, clear cache partition, etc. but no luck. I've tried everything under Android 6.0 here but it continues to bootloop no matter what I do.
It's not rooted and the bootloader is locked, so I don't think I can even install TWRP or any custom recovery. I have never even though of enabling USB debugging so that's out of the question. What's odd is after trying all sorts of things, sometimes, after the phone has been off for a while I would power it on and it would actually boot into the Welcome screen. Shortly after that though, it locks up and starts bootlooping again. I don't know what else I can do about this or if it's recoverable. I hope someone can help. If it's of any significance, when in recovery mode, at the top I see what I think is the firmware it's currently on -- motorola/clark_retus/clark 6.0/MPHS24.49-18-4/5. Please help!

Update - After having my XT1575 powered off overnight, I powered it on this morning and it was able boot all the way into the Welcome screen, setup, etc. Right away I went and turned on USB Debugging and Allow OEM unlock. Tried rebooting and again it fails to boot. What's weird is it randomly seems to boot when it wants, and something must be corrupt but I just don't know what it could be. Does anyone have any ideas?

Don't unlock the bootloader.
If it is locked and behaving that way you should be able to get a warranty fix out of Lenovorola. If you unlock the bootloader you void your warranty, and they might choose to not honor it even if you say the problem started before.
Painful and slow as it might be, I'd recommend working with the manufacturer on this one.

jason2678 said:
Don't unlock the bootloader.
If it is locked and behaving that way you should be able to get a warranty fix out of Lenovorola. If you unlock the bootloader you void your warranty, and they might choose to not honor it even if you say the problem started before.
Painful and slow as it might be, I'd recommend working with the manufacturer on this one.
Click to expand...
Click to collapse
Yes undo what you just did an follow this guy

jason2678 said:
Don't unlock the bootloader.
If it is locked and behaving that way you should be able to get a warranty fix out of Lenovorola. If you unlock the bootloader you void your warranty, and they might choose to not honor it even if you say the problem started before.
Painful and slow as it might be, I'd recommend working with the manufacturer on this one.
Click to expand...
Click to collapse
I'm afraid it's too late for the bootloader, since it was one of the things I was trying out of desperation. After trying fastboot flashing the stock firmwares, I still get bootloops and strangely enough I was able to use the phone the other day for several hours before it started bootlooping again Thing is, it seems to behave differently at random times. Sometimes it makes it all the way up to the "Android is upgrading" screen but then freezes and reboots.. Other times it locks up at the Motorola splash screen and reboots.. And sometimes it even boots all the way up, is usable for a little bit, then begins bootlooping on its own.
I'm just wondering if something is corrupt software-wise (boot? system? etc?) or if it's a hardware issue. How do I even tell at this point?

iflyimpilot said:
I'm afraid it's too late for the bootloader, since it was one of the things I was trying out of desperation. After trying fastboot flashing the stock firmwares, I still get bootloops and strangely enough I was able to use the phone the other day for several hours before it started bootlooping again Thing is, it seems to behave differently at random times. Sometimes it makes it all the way up to the "Android is upgrading" screen but then freezes and reboots.. Other times it locks up at the Motorola splash screen and reboots.. And sometimes it even boots all the way up, is usable for a little bit, then begins bootlooping on its own.
I'm just wondering if something is corrupt software-wise (boot? system? etc?) or if it's a hardware issue. How do I even tell at this point?
Click to expand...
Click to collapse
The random nature of what you're describing does sound like hardware. Consider a full restore where you fastboot flash everything back to stock of you haven't already.
Check logs. See if you're getting anything in last_kmsg. Use an app like syslog if you aren't used to pulling them, though you might have to use adb if you aren't getting through boot all the time.

jason2678 said:
The random nature of what you're describing does sound like hardware. Consider a full restore where you fastboot flash everything back to stock of you haven't already.
Check logs. See if you're getting anything in last_kmsg. Use an app like syslog if you aren't used to pulling them, though you might have to use adb if you aren't getting through boot all the time.
Click to expand...
Click to collapse
Thanks for replying. I've tried fastboot flashing everything and even going into recovery and clearing cache partition as well as doing a factory data reset. I'm afraid it may very well be hardware. I'll try your suggestion about the logs.
Is 'last_kmsg' a line I should be looking for in the log? If so, what would I need to see in order to determine whether or not it's a hardware problem?

iflyimpilot said:
Thanks for replying. I've tried fastboot flashing everything and even going into recovery and clearing cache partition as well as doing a factory data reset. I'm afraid it may very well be hardware. I'll try your suggestion about the logs.
Is 'last_kmsg' a line I should be looking for in the log? If so, what would I need to see in order to determine whether or not it's a hardware problem?
Click to expand...
Click to collapse
/proc/last_kmsg is a log file that should get written to if a kernel panic causes a reboot in theory. In practice I find it is often blank even after a random reboot.

iflyimpilot said:
I'm afraid it's too late for the bootloader, since it was one of the things I was trying out of desperation. After trying fastboot flashing the stock firmwares, I still get bootloops and strangely enough I was able to use the phone the other day for several hours before it started bootlooping again Thing is, it seems to behave differently at random times. Sometimes it makes it all the way up to the "Android is upgrading" screen but then freezes and reboots.. Other times it locks up at the Motorola splash screen and reboots.. And sometimes it even boots all the way up, is usable for a little bit, then begins bootlooping on its own.
I'm just wondering if something is corrupt software-wise (boot? system? etc?) or if it's a hardware issue. How do I even tell at this point?
Click to expand...
Click to collapse
going by that logic the thing that you should have done was get a factory image from moto and flash to stock using moto tools if that failed at fixing it then send into moto it might not be lost yet but the more you progress the more less likely to replace the phone moto is...
it sounds like something is going bad could be ram emmc or the soc
What i would do is get into discussions with lenovo to see if they can get you fixed up. if you unlocked the bl they know be straight with them. if you get nowhere and no rom you load can fix it sell as parts replace at your expense...

Continuous Bootloop even after stock flashed

Hi.
I've had numerous nexus phones and generally dont have many issues however randomly today my phone entered a bootloop. I decided to completely flash stock firmware (how i normally solve issues but no matter what I do it just continues to bootloop.
I can get into Fastboot but thats it.
Any ideas or experience of this anyone?
Thanks in advance

Gave up in the end, couldn't fix it.
google replacing under warranty

Just had to do the same thing last week. Using Uber Partner app and when I accepted a "call" phone crashed and began bootlooping. Tried fastbooting stock image but ended with "Phone is Corrupt" message and continuous boot loop before replacing under warranty. I was running August update Benzo ROM. Never experienced anything like this before and I've been flashing for 5 years now. Sorry about your device, the new one in the mail will make it all better best phone ever!

Oh god... I think my device is doing the same thing.... I've tried flashing stock through fastboot twice now. Still saying my device is corrupt. Even tried a different cable, and redownloading the firmware.

Stretlow said:
Gave up in the end, couldn't fix it.
google replacing under warranty
Click to expand...
Click to collapse
This happened to me too the same day out of nowhere. Google sent me a refurb. Battery in this replacement seems much better. I couldn't even get into the recovery.
Sent from my Nexus 6P using Tapatalk

Random reboots after nougat update

Anybody else's phone rebooting every few days..?
It hard reboots (Galaxy S7 edge screen), so i thought it might be hardware failure.
Haven't downgraded to 6.0 to check.
I don't have an sd card inserted (because the one i had corrupted which caused my phone to randomly reboot, now i took it out and it still does it)
Also, I noticed that every time it randomly reboots, the battery percentage drops significantly.
G935F, stock

re: reboot issues
wpbogdan said:
Anybody else's phone rebooting every few days..?
It hard reboots (Galaxy S7 edge screen), so i thought it might be hardware failure.
Haven't downgraded to 6.0 to check.
I don't have an sd card inserted (because the one i had corrupted which caused my phone to randomly reboot, now i took it out and it still does it)
Also, I noticed that every time it randomly reboots, the battery percentage drops significantly.
G935F, stock
Click to expand...
Click to collapse
Before you updated to nougat 7 did you do a full and complete wipe
which includes wipe system, data, cache, dalvik cache and last but
not least did you do a factory reset in twrp recovery before odin
flashing the Nougat firmware?
Are you 100% sure that you odin flashed the correct Nougat 7 firmware for your S7 Edge?
Flashing the wrong firmware can cause rebooting issues and fast battery drain.
Flashing without doing a full and complete wipe can cause rebooting issues too.
Good luck, have a great day!

Misterjunky said:
-snip-
Click to expand...
Click to collapse
well, i had a clean 6.0 install which upgraded to 7.0 via ota (UK BTU firmware),but thanks i suppose
(and i also factory reset 7.0 many times)

I am getting random reebots since nougat. I flashed the bell nougat (in on Rogers in canada) and then flashed the Rogers CSC. Things seem to check out so I'm not sure what's wrong. I am going to try to get the Rogers nougat files and see if that addresses the issue.
Sent from my SM-G935W8 using Tapatalk

I have the same issue.... I have unlocked phone on a thai carrier

You DO NOT have to do a 'factory reset' every time you have an update, not even for an operating system update.
I don't know where this comes from but it's stupid.
These updates are designed to integrate with existing systems!
You are as likely to solve any issues with a few reboots.
If you have a problem it's likely due to software conflicts of an app you've installed, not the operating system. Android is pretty good sorting itself out.
So, you do a factory reset with all the hassle of trying to get things back to where you were and then you install another app which causes an issue and ...
Pointless as are the cache wipes always suggested. Android is good at managing resources.
At least with a cache tidy up you're not back to square one
I wished folks would stop suggesting factory resets at every opportunity. Mad.

I get them too, i`m on the lastest NEE software updated via ota. Randomly, when i get it out of the pocket, it says enter pin number because your phone was restarted, i`m using fingerprint lock.

Hello I have a Galaxy S7 and since the update to Android Nougat 7.0, my phone restarts randomly, it can stay an entire week without restart and it can also restart 2 days in a row. It's totally random. I have reset to the factory settings and I have reinstalled only the most important applications (facebook messenger, viber, yahoo mail) but unfortunately about ten days after reset, the problem has reappeared. What could be the cause of this problem? For info, the firmware version installed on my phone is: G930FXXU1DQBO. Also, I saw on SamMobile that the countries that received the update later, had a new version. Could the problem come from that? Is this a bug in the firmware installed on my Galaxy S7. Thank you in advance for your help.

Sadly I have the same problem. Oddly enough this is my first handheld which I didn't root and the first I am running into such issues with.
Got a OTA update to Nougat and I am getting almost daily random restarts.
I wasn't able to discern any patterns so far. Sometimes while it is charging, sometimes just being in my pocket. It doesn't run hot as if an app is running havok nothing.
So far I cleared the cache and that seemed to help but alas it started again.
Does anyone have an idea what is left to try? I would do a complete wipe, but others reported that it did jack for them so I am hesistant to try it.

Sorry for My bad English, i m italian.
Try to remove Chrome. The issues is there for me.
Bye

I have some problem. Not to mention battery life severely reduced after update to nougat. usually 5h screen on time to now 2.. max 3h. SAD.

Samsung Galaxy S8+ Random Reboots
Same problem with my Samsung Galaxy S8+ running Nougat. Purchased the phone from AT&T and received it 3 days ago. It randomly rebooted twice so far, once when I was looking at photos and once when using the play store

Olynth said:
I get them too, i`m on the lastest NEE software updated via ota. Randomly, when i get it out of the pocket, it says enter pin number because your phone was restarted, i`m using fingerprint lock.
Click to expand...
Click to collapse
I have the same problem. It is completely random, it can happen every 2 days or once a week. Even after a factory reset, this problem of random reboots still persists. The firmware version is G930FXXU1DQBO and I still have not received a new update. Have you solved your problem?

GeekTN said:
I have the same problem. It is completely random, it can happen every 2 days or once a week. Even after a factory reset, this problem of random reboots still persists. The firmware version is G930FXXU1DQBO and I still have not received a new update. Have you solved your problem?
Click to expand...
Click to collapse
Same here sometimes once a month, sometimes twice a day. No idea why. Probably its Sammy

xantrk said:
Same here sometimes once a month, sometimes twice a day. No idea why. Probably its Sammy
Click to expand...
Click to collapse
Do you reset your phone to factory settings? What is your firmware version? It seems that the old versions are not very stable.

GeekTN said:
I have the same problem. It is completely random, it can happen every 2 days or once a week. Even after a factory reset, this problem of random reboots still persists. The firmware version is G930FXXU1DQBO and I still have not received a new update. Have you solved your problem?
Click to expand...
Click to collapse
No, the problem is still here, i did not receive any software updates so far. Sometimes it reboots even twice a day, random, sometimes 2-3 weeks without reboot. Waiting for ota update, maybe it will solve it.

GeekTN said:
Do you reset your phone to factory settings? What is your firmware version? It seems that the old versions are not very stable.
Click to expand...
Click to collapse
Resetting on february build helped. Reboot free since almost one month. But im sure it will come back, It did before.

xantrk said:
Resetting on february build helped. Reboot free since almost one month. But im sure it will come back, It did before.
Click to expand...
Click to collapse
After receiving the February version, did you receive a corrective update? If this is the case, it may be the update that has solved your problem.

My galaxy s7 have the same issue, rom Brazil zto, full cache wipe data, reinstall rom, i don't know what to do it,

robertorochajr said:
My galaxy s7 have the same issue, rom Brazil zto, full cache wipe data, reinstall rom, i don't know what to do it,
Click to expand...
Click to collapse
Since when did the restarts start? What is the firmware version number of your Galaxy S7?