Related
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
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:
Hello, I just want to share with you strangest problem I ever had with Android device.
I have old Nexus 7 nakasi with stock 5.1 rooted. Past few weeks tablet was unused, charging from USB port in Sony Bravia TV.
Yesterday I've tried to use again, but I realized that it was turned off. After switching on and connect to wifi, he rebooted after a few minutes.
I found that without wifi lasts about 10 minutes before it restarts.
Strangest thing:
After each reboot, he booted into absolutely identical state. No matter that I uninstalled application, app was back, deleted files was back. But also all the changes of the past were gone.
I tried boot to save mode – after while he rebooted too
I tried leave tabled few hours in TWRP recovery - he has not rebooted, so he’s not unstable
I tried delete cache – no change
So I tried factory restore – after reboot he booted without change, hmm…
So I download nexus image a start “flash-all.bat”. No error, but after reboot. Surprise – no change – my old rooted system.
Via TWRP recovery I tried format/wipe everything, no change I even change filesystem from ext4 to F2FS – after reboot data are back
If I make backup in TWRK into internal memory (boot for instance), backup completes ok, but after reboot backup is gone.
If I start big backup (3gb data) into internal memory, backup fail after few minutes. But backup via otg to usb flash disk completes OK. So I can create full system+data backup.
It’s like flash memory is damaged and allow write only a small amount of data. And after reboot is restored to identical state. That would explain why Android reboots after a while, and recovery not.
What do you think? Can it be anything else than damaged flash memory? And if so, is there anything i could try, or "Zed is dead"
And finally it’s possible that Sony TV cause this? Thank you and sorry for my bad English.
Exact same thing happened to me, Bought a new motherboard for around $20 online... ebay I think and fixed it good as new... plus i upgraded to the 32GB model! replacement was pretty easy, I have never done anything like this before but didn't encounter any problems. I think its due to the flash memory dying, and becoming read only. I even formatted the whole drive from my computer and when I rebooted, Exact same old system. Here's the iFixit guide I followed: https://www.ifixit.com/Guide/Nexus+7+Motherboard+Replacement/9943
Happened to me too, and I also just replaced the motherboard. I have a feeling the equivalent of the boot sector fails, but on a ssd that puts the drive in read only mode. I seem to recall a fix using a non standard partitioning tool whose name escapes me, but our normal flash and recovery tools won't work. I wanted 32 meg upgrade anyway so decided it was best to replace rather than repair.
Sent from my Nexus 7 using Tapatalk
---------- Post added at 12:48 AM ---------- Previous post was at 12:43 AM ----------
Ah, tool is called NVFlash, but been years since I used it so can't help with instructions.
Sent from my Nexus 7 using Tapatalk
Thank you all for reply. Unfortunately cheapest 32GB motherboards on ebay cost 45$. But but I'm afraid that 32 gigabytes version will not be much faster. Nexus 7 has a terribly slow storage. Recently i bought Onda tablet V891, for 140$ and it's and it's perfectly fast device
When I think about it, the problem was caused by Titanium backup backuping every day. Finally, a flash memory did not last.
Thank for NVFlash I'll try to write here how it went
I just bought a nexus 7 / 32g with a broken screen for about 25$. Used, but worked. And now have a few extra parts...
Sent from my Nexus 7 using Tapatalk
So while i had my phone in my pocket while at work as i had done thousands of times before but now all of a sudden i take it out to check a message and the phone reset itself and wiped my internal storage and sd card of all videos pictures and music. so im pissed about that but then the dreaded one ui update rolled around and just made for an even more frustrating night.
So im asking for help for 2 problems; Hopefully restoring all that data from the SD card and rolling back to oreo.
Im new to the forums havent done any kind of firmware messing around so help in much detail would be appreciated thank you.
if it makes any difference its a SM-G950U on Verizon
Restored myself back to oreo but still havent found a way to restore the sd card data. it was a LOT of pictures.
Use a recovery software with the sd card plugged in a computer with Windows
Hello guys, I've a nexus 6p that doesn't starts. I was wondering that was caused by the well known problem, but my particular phone is stuck on "balls" bootanimantion... So I think it isn't related to the snap810 problem.
I should say that the smartphone was completely out of memory, no MB of storage left. Maybe this is the problem?
I should apply the known methods to solve bootloop?( I mean... Flashing modified kernel...)
I tried also wiping cache with no result.
I didn't already made a factory reset because the owner asked me if I can save photos.
Thanks.