So this morning when I woke up, I went to charge my phone because it was out of juice. After charging it awhile, I turned it on again, only to be confronted with a screen that says "Type password to decrypt storage", and it gives me the option of making an emergency call or decrypt. I have read various forums, including one in the Nexus 7 area which describe people having this issue. My HTC had been running Venom One 4.3.0.
What I've tried/know so far:
1. I can reboot into recovery and TWRP v2.6.3.4 pops up just fine. However, it also asks for my password, which I can bypass by hitting cancel.
2. I have tried to factory reset, but after about 5 seconds, it says failed, during "Updating partition details"
3. I have tried to advanced wipe, but it will only let me wipe cache, and not data nor Dalvik cache.
4. I can't restore anything because nothing shows up under restore.
5. If I go to restore, the size of the various parts (data, system) seems right, but I can't back anything up. It always fails during "Updating partition details"
If anyone can be of any help, it would be greatly appreciated! I'm not super techy, but I'm willing to try whatever at this point. I'm pretty much resigned to losing all my data, which isn't a huge deal; I believe most of my stuff is backed up.
If someone can say definitively that I'm SOL, then let me know. At least I know I can move on. Some have suggested that this could be a hardware failure related to my flash memory, in which case, I don't think there's anything I can do (unless there is).
There is no work around for this...the storage is encrypted, only way around it is to format data and push a rom back to storage via adb and then reflash...
copy rom to where your adb files are,boot into twrp recovery run this command after you format your data partition...it will push the rom to the phone, may take awhile so be patient and you wont see any progress until it finishes.
adb push nameofrom.zip /sdcard/.
Wonders_Never_Cease said:
There is no work around for this...the storage is encrypted, only way around it is to format data and push a rom back to storage via adb and then reflash...
copy rom to where your adb files are,boot into twrp recovery run this command after you format your data partition...it will push the rom to the phone, may take awhile so be patient and you wont see any progress until it finishes.
adb push nameofrom.zip /sdcard/.
Click to expand...
Click to collapse
Thanks for the help...but I guess I had forgot to mention that my computer no longer recognizes my phone any more...so am I really SOL then?
maximus.oj said:
Thanks for the help...but I guess I had forgot to mention that my computer no longer recognizes my phone any more...so am I really SOL then?
Click to expand...
Click to collapse
use an Ubuntu live CD
Related
VEGAn RC1 Ginger Edition was loaded and working fine for almost two weeks.
Then I powered up and it would get stuck on the G-TABDEVs splash screen.....
Here is what I can do:
I can power up and the tab will go past the viewsonic birds screen to the next splash screen (G-TABDEVS) and will stay there indefinately.
I can power up into Clockworkmod 2.5.1.1. 0.8 (all soft buttons work and I can scroll through the choices with the vol switch just fine)
I can wipe cache partition
I can apply sd card:update.zip (only because I still have VEGAn RC1 GE .zip on my device)
I can mount the USB drive (drive is recognised on my computer running win XP)
I can apply NVflash to the device (did this to get access to CWM by changing part #9)
What I can't do:
I can not transfer large files files from my computer to the tablet (I can make a directory and transfer small files only maybe 100 kb or less) Any time I try to transfer a larger file (a ROM or other) I get an I/O error.
I can not partition the SD card (internal storage),
Wide data/factory reset,
Wipe Delvik cache,
it just hangs indefinately with each of the above.
I have spent counless hours searching through all the great information on XDA and can not find any instance like mine.
I don't think it has been bricked because of what I still can access, although there still seems to be something "limiting" my actions.
Has anyone experienced this? and more importantly.... Can anyone HELP????
you can boot into clockwork but cant use the factory reset option there? if its hanging how long did you let it wait? id try a reset and let it sit for 5-10 mins to see if its really doing something or just mucking around.
you make a restore file (backup of your previously installed rom on your tablet)?
if the rom is still on your tablet try reinstalling it. then after installing try factory reset before rebooting. if you cant reset try reboot then reset.
the G-Tabdevs screen staying there indefinitely is because it needs to be reset. so you just have to figure out how to reset it.
Great! I totally did not realize that it took that long to reset. I will try that later tonight and post my results.
OK, I tried using "wipe data/factory reset" and it just hung. I let it sit for 20 minutes (just in case).
Then tried "partition SD card (2048,0) and let it run, again for 20 minutes and it just hung.
Still very frustrated.
What are my options at this point?
I need to follow this thread b/c I have the same problem. Last night shut down fine and this morning went to power back on and I get the birds and then it gets stuck in the next load screen. I reinstalled update.zip but no dice. Any ideas?
Make sure all the partition are active, wipe dalvik, try reflashing the same rom over and fix permission
For such strange issue you can alway use the nvflash format utility but not before having performed an nvflash backup then use bekit images to bring back the tablet to life. You can also make a clockwork backup
Backup http://forum.xda-developers.com/showthread.php?t=1010659 (if something goes really wrong it can help, the .bct is what you want to keep at least)
Be warned that backup may have issue if you got flash bad block, this is not a critical issue
Format http://forum.xda-developers.com/showthread.php?t=974422
Restore http://forum.xda-developers.com/showthread.php?t=861950
make sure you follow instruction
This thread has link to everything!
http://forum.xda-developers.com/showthread.php?t=1026660
Keep in mind that NVFLASH only restore or erase about 300MB of the 2GB out of the 16GB you can write to.
This is in no way a FULL tablet reset. It is however a dangerous tool above application are tested and proven, some older thread may have nvflash command that can be dangerous.
That is great information.
I have used the format flash, then Nvflash.
flashes work fine, but same issue. Stuck at G-tablet splash screen.
I still can not load update.zip because I can not transfer any large files to the tab when it is mounted.
Any time I try and transfer a file greater than about 100k I get an error that states "can not copy file due to an I/O error"
Really disheartening........
If one enables full device encryption in Ice Cream Sandwich, am I correct in assuming that that the internal SD of that device is now not going to be available in the CWM recovery mode? And even if it was, the root fs would not be available? If so, this pretty much would make CWM flashing your device near impossible?
Does CWM even work if you use FDE? Or is it planned/
The question I guess is, when do you input your encryption password? Is it some pre-boot step?
I really want to enable device encryption but I can't find enugh details on how it works.
I did read this post on it., but it doesn't really answer my questions. And it is unclear if it encrypts the internal SD, or just the root FS?
http://source.android.com/tech/encryption/android_crypto_implementation.html
No one knows anything about this?
I got a Gnex today from Verizon in the US and I encrypted my phone after I unlocked the bootloader but before rooting. As a result I don't think I will be able to root because it doesn't seem that the modified boot.img that the instructions tell me to use can mount the encrypted system (it sat at the Google logo w/ the unlocked icon for 10 minutes before I pulled the battery and let it boot the stock boot.img) which came up fine.
It seems the only way to decrypt the phone is by doing a factory reset.
That's all I know. That being said, while a custom recovery may work for wiping partitions (such as cache), it would probably be mostly useless until the custom recovery is updated to support the encrypted file systems. I'm a *NIX user and an engineer, but don't have a lot of experience with Android's internals, so take all that with the appropriate sized grain of salt.
Regards,
Chris
Bump.
Anyone experimented with full device encryption / ROM flashing / SD Card? I'm curious about this as well, but not curious enough to experiment.
I dident try it myself, so i dont exactly know, how this works. But i think device encryption shouldent completly block clockworkmod recovery.
I think it could be a problem to make a backup while your device is encrypted. But i think it shouldent be a problem to recover a old system over an encrypted one. Encryption keeps people without the key away from reading data. This dosent mean you cant wright something over it and replace the locked data with some new one. But then you defenitly loose the old data. I dont think you can flash a new ROM or a recovery without a full wipe. You probably gona loose all the data you had on the old system.
But i general i think this is anyway a good think to do when you flash a new ROM.
I think you could give it a try, without briking your phone. But i dident try it, so i cant take any responsibility.
Would any of you happen to know how to get to the diagnostic mode?
ryfly65 said:
Would any of you happen to know how to get to the diagnostic mode?
Click to expand...
Click to collapse
I sonst exactly know hat diagnostic Mode you mean. Depends hat Diagnose you want to run. Do you want to read the logfiles in your phone, wher you can see what ist doing? You could use the app alogcat. An other way would be to run logcat over Eclipse.
Sent from my HTC Desire HD using XDA App
Hilmy said:
I sonst exactly know hat diagnostic Mode you mean. Depends hat Diagnose you want to run. Do you want to read the logfiles in your phone, wher you can see what ist doing? You could use the app alogcat. An other way would be to run logcat over Eclipse.
Click to expand...
Click to collapse
I need to edit modem information and enable a diag port for QPST, essentially allowing me to flash it to another carrier.
Is there any new information on this? Any help would be very appreciated!
Sent from my Galaxy Nexus using XDA App
I encrypted mine after flashing the stock ICS 4.0.3 image and rooting. CWM still loads, but when I try to use USB mass storage, windows tells me it needs to be formatted before the SD card can be used.
You can use titanium backup to make backups of your stuff, and restore them to a non-encrypted phone. I have found no other way to unencrypt the phone than factory reset either. When you encrypt, then go to settings > security > encryption, it just has a greyed out area saying "Phone is encrypted", which is stupid and needs to be fixed.
nevarDeath said:
I encrypted mine after flashing the stock ICS 4.0.3 image and rooting. CWM still loads, but when I try to use USB mass storage, windows tells me it needs to be formatted before the SD card can be used.
You can use titanium backup to make backups of your stuff, and restore them to a non-encrypted phone. I have found no other way to unencrypt the phone than factory reset either. When you encrypt, then go to settings > security > encryption, it just has a greyed out area saying "Phone is encrypted", which is stupid and needs to be fixed.
Click to expand...
Click to collapse
So if I factory reset the device from CMW I will not loose my pictures or TB in the internal SD?
What about flashing a new ROM?
Thanks!
I have been playing with ICS + FDE for several days doing different things. First off this is:
Nexus S 4G, running Pete's crespo4g OTA ROM
I flashed with CWM which is still on there and runs fine.
However: /data and /sdcard and /system (?) are encrypted and CANNOT be mounted.
To restore you have to 1) make a full backup over USB to a PC of the whole SDcard (or at least the important folders).
2) wipe and reformat everything. This isn't just a factory reset, this kills the sdcard as well.
3) mount (hopefully) the newly reformatted /sdcard and blow your backup from the PC onto the /sdcard
4) use CWM to restore a previous ROM.
That's pretty much it, give or take. Not for the faint of heart. However, if you are concerned enough to want encryption, you don't want to just say reboot recovery and voila all your files are belong to us, right?
---------- Post added at 03:58 PM ---------- Previous post was at 03:34 PM ----------
Also, the backup to PC part is just your sdcard. It doesn't back up the whole system. There might be a way to do that via adb, I don't know.
So i am running rooted runnig miui.us rom. I just tried to encrypt phone.. It ran for 2 and a half hours and I got impatient. thinking maybe i shouldnt have done it... Then after a little bit of panic i said **** it if i lose data i lose data... so i powered off and back on hoping i didnt and the rom booted back up with all my data intact..... •••••• Wish I had more to report but im not doing that again until someone can confirm that it works fine...... I have tried booting into cwm yet.. If i have an issue when i need to boot illl report back but if you dont hear from me here then assume I was able too.
Pete's to CM9 - still encrypted
IT does indeed take a fairly long time to encrypt. If I understand correctly it will build the encrypted partition on a loopback (or something like) before erasing the original (by overwriting?).
I've got more to report. I followed my plan (couple posts back) for unencrypting and reflashing my phone. (Nexus S 4g).
The first bits of this worked fine. I was able to flash CM9 onto my phone (works like a champ btw). While the phone was in recovery I mounted the SD and copied my backup back onto it.
However...
When CM9 booted I STILL got the "unlock your device" screen, still the same password, and it decrypted and booted. That was surprising, but not as much as when I looked for the SD card, it said it was incorrectly formatted! The only thing to do was reformat and copy with the phone on and unlocked.
So lessons learned: 1) a factory reset from _inside_the_ROM_ doesn't remove the encrypted partition at all and
2) As far as I can tell, the SD card _is_ encrypted along with /data
I'd be very interested to hear other's experiences, especially someone who can remove their SD storage.
Undoing FDE
First off - Lacking a device with removable storage to test with all I can tell you is that the sdcard is not accessible by any normal means after FDE is enabled without booting into the encrypted system.
"Removing" FDE required three steps beyond normal:
-Factory reset from within the ROM
-factory reset/wipe at recovery and/or format /data
-once into a running ROM, reformat the sdcard
Once all that is done (in addition to normal setup for ROM) you should be able to operate normally again.
problem with encryption on sgs2 with android 4.0.3
I really want to enable my device encryption too, but I can't !!!
the phone start encrypting after he ask me for a new secure password, rebooting and asking again for my password and surprise!!!.... the password is not match ?!?!
I repetead these steps for 3 times but the same result...the password does not match!!! ?
Please, if someone found a trick to repair this inconvenient, tell us in this post steps to be followed.
Regards!
SGS2, Android Icecream 4.0.3
leech2082 said:
So i am running rooted runnig miui.us rom. I just tried to encrypt phone.. It ran for 2 and a half hours and I got impatient. thinking maybe i shouldnt have done it... Then after a little bit of panic i said **** it if i lose data i lose data... so i powered off and back on hoping i didnt and the rom booted back up with all my data intact..... •••••• Wish I had more to report but im not doing that again until someone can confirm that it works fine...... I have tried booting into cwm yet.. If i have an issue when i need to boot illl report back but if you dont hear from me here then assume I was able too.
Click to expand...
Click to collapse
I did exactly what you did, and so far everything seems to be intact Thanks!
I wanted a clean cyanogemod installation on my desire z so I followed this guy's advice:
For a clean install, just boot into recovery, format the /system partition (found under the Mounts and Storage menu) and then perform a Factory Reset/Data Wipe. After that, you are good to install CM and gapps. This does not erase your sdcard, so if any apps stored stuff on there, it will still be there unless you manually erase it.
Click to expand...
Click to collapse
I didn't think it through and restarted the phone thinking I'd use clockworkmod to reflash the cyanogenmod rom. When I turn it on now it just displays the green 'htc' text on white background, none of the buttons do anything.
I've still got adb etc installed from rooting a year ago, is there a way I can unscrew this up? A million thanks.
Edit: When I start it and go to the loader screen by holding down the optical button, it gives me 'bootloader' as an option but when I select it, it looks like it scans the SD, tells me there is no image and offers to start an update. I can see it with adb but can't get a shell, it says - exec '/system/bin/sh' failed: No such file or directory (2) -'. Is there a boot file I can push onto it?
Read one of THESE.
I believe adb push a ROM and gapps to /SD card.
Sent from my EVO using xda premium
It seemingly randomly booted in cwm recovery after about 30 on-offs and I loaded the cyanogen rom, not a satisfying fix but I'll take it. Thanks for your help.
hello all,
I am having some hanging problem in my fone. One of my friend ask me to format phone but dont know how to format it.
Can any one help me??
gorwani12 said:
hello all,
I am having some hanging problem in my fone. One of my friend ask me to format phone but dont know how to format it.
Can any one help me??
Click to expand...
Click to collapse
I am sure your friend just meant to master reset your phone. (It's essentially formatting your phone as it deletes everything.) Please be aware of that and remove anything you might want to keep - pictures, videos, etc..
Now to do this you'll need to go into Settings and then go to Backup & reset. From there it will walk you through the remainder of steps.
Sent from my HTC One using xda premium
go to the offical recovery and make the double wipe.
gorwani12 said:
hello all,
I am having some hanging problem in my fone. One of my friend ask me to format phone but dont know how to format it.
Can any one help me??
Click to expand...
Click to collapse
It depends on what you mean by format phone. Are you wanting to completely format everything including your SD Card? I was also in a similar situation where I had suspected that I had some data somewhere taking up space but I couldn't find it. So here's what I did.
*Make sure you have ADB properly set up prior to this.
Code:
1. Run Titanium Backup. I used the Back up all user data, and back up all system data (deselected all and then chose the ones I wanted)
2. Nandroid backup your current rom
3. Back up your SD Card
4. Use TWRP and select wipe > advanced > wipe all (something similar to that)
5. This will leave your phone completely blank and fresh as if it were new, only no bootable os or files on your sd card
6. Reboot recovery
7. Have a rom that you'd like to install in your adb\platform tools folder (or where ever your ADB resides).. Rename it something nice like rom.zip
8. Have cmd open and cd to where your adb is (mine is C:\sdk\tools)
9. Run this command: adb push rom.zip /data/media/
10. This can be about a 10 minute wait. Don't do anything until it finishes. When it's finished you'll be able to type in another command
11. Reboot recovery
12. Flash Zip
13. Once that zip is finished reboot and allow it to boot up.
14. Now, you can use this rom to put everything back on your SD Card including your nandroid/Titanium Backup
15. Once everything copies over reboot into recovery and restore your nandroid.
I had installed Android Revolution HD custom rom and it was running perfect, but I decided I liked Viper rom more. I had viper rom on my phone storage so I performed the wipes and successfully flashed viper rom. However, when viper rom finished installing and setting up, I was met with a decrypt storage page right after the unlock screen with infinite attempts to guess a passcode I never set. What I did was try searching online for hours and eventually realized I was stuck in Philz Touch or the decrypt password screen so I factory reset, Dalvik cache cleared, and everything to the point where now I seem without any hope of being able to get anything onto the phone ever. Am I bricked?
Relax, you aren't bricked. If the screen still comes on, you can recover. Its just a matter of knowing how to do so.
Its not clear based on your description what the current state of the device is. Still stuck with the decryption password screen or recovery? Factory reset likely isn't going to do anything if you can't boot into OS; as all it does is wipe user data.
Did you make a nandroid of your previous ROM? If not, why the heck not?
If no nandroid, adb push a different ROM to the device. Then flash the ROM from recovery.
redpoint73 said:
Its not clear based on your description what the current state of the device is. Still stuck with the decryption password screen or recovery? Factory reset likely isn't going to do anything if you can't boot into OS; as all it does is wipe user data.
Did you make a nandroid of your previous ROM? If not, why the heck not?
If no nandroid, adb push a different ROM to the device. Then flash the ROM from recovery.
Click to expand...
Click to collapse
I had a backup before but now I can't access the sdcard (internal storage) and so nothing from recovery menu seems to work. I have tried adb sideloading and it says *cannon read ' ' *. Will I be able to adb push to a phone that can't recognize it's own internal storage?
demozillar said:
I had a backup before but now I can't access the sdcard (internal storage) and so nothing from recovery menu seems to work. I have tried adb sideloading and it says *cannon read ' ' *. Will I be able to adb push to a phone that can't recognize it's own internal storage?
Click to expand...
Click to collapse
I got ADB sideload to work with cyanogenmod, I think im out of the black, thank you for your help friend
demozillar said:
I had a backup before but now I can't access the sdcard (internal storage) and so nothing from recovery menu seems to work. I have tried adb sideloading and it says *cannon read ' ' *. Will I be able to adb push to a phone that can't recognize it's own internal storage?
Click to expand...
Click to collapse
With the phone connected to a PC, go to device manager, find the internal memory and format it.
Did you factory reset in bootloader? I suspect this corrupts the internal memory.
adb push won't work if the internal memory is corrupt. Don't know about sideload. Even if you flash the ROM, I don't think it will function correctly if it can't write to internal memory. You need to format the memory to sort that out.
Also, adb sideload can be finnicky. I've seen it fail lots of times when adb push works fine. But if you can get to work, good for you!
redpoint73 said:
With the phone connected to a PC, go to device manager, find the internal memory and format it.
Did you factory reset in bootloader? I suspect this corrupts the internal memory.
adb push won't work if the internal memory is corrupt. Don't know about sideload. Even if you flash the ROM, I don't think it will function correctly if it can't write to internal memory. You need to format the memory to sort that out.
Also, adb sideload can be finnicky. I've seen it fail lots of times when adb push works fine. But if you can get to work, good for you!
Click to expand...
Click to collapse
Yes you are right about factory reset in bootloader, that was my mistake I guess. the adb sideload was able to push through even though adb push was being denied. Thanks again for your help
demozillar said:
Yes you are right about factory reset in bootloader, that was my mistake I guess. the adb sideload was able to push through even though adb push was being denied.
Click to expand...
Click to collapse
Interesting that sideload works, while push doesn't. And not what I would expect. My understanding of sideload, it still pushes the ROM to internal memory then flashes it. Just does it all with a single adb command. So if internal memory is corrupt, I would expect to fail to push, same adb push.
Factory reset in bootloader is a honest mistake. I was only suspicious of this, since the same "bug" occurs on the One X (EVITA), where on modded phones, doing a factory reset in bootloader corrupts the internal memory. One would expect it to perform its intended function the same as factory reset in recovery or within the OS (which both should work fine).
redpoint73 said:
Interesting that sideload works, while push doesn't. And not what I would expect. My understanding of sideload, it still pushes the ROM to internal memory then flashes it. Just does it all with a single adb command. So if internal memory is corrupt, I would expect to fail to push, same adb push.
Factory reset in bootloader is a honest mistake. I was only suspicious of this, since the same "bug" occurs on the One X (EVITA), where on modded phones, doing a factory reset in bootloader corrupts the internal memory. One would expect it to perform its intended function the same as factory reset in recovery or within the OS (which both should work fine).
Click to expand...
Click to collapse
The thing about sideload was you could initiate it into sideload mode (or whatever) and then use the adb sideload command, perhaps it would have worked with adb push if I knew more what I was doing but just simply adb push " " would not work. And yes I had a good scare when I pressed the factory reset, went into recovery and saw I deleted my zip files
demozillar said:
The thing about sideload was you could initiate it into sideload mode (or whatever) and then use the adb sideload command, perhaps it would have worked with adb push if I knew more what I was doing but just simply adb push " " would not work.
Click to expand...
Click to collapse
adb push does not require the phone to be in any particular mode (like adb sideload does), and should work as long as the phone is on. It could be that sideload pushes to some partition that is not corrupt. Just a guess.