Hello,
I woke up this morning and have been faced with the Encryption Unsuccessful error message. What's weird, is that I haven't done anything special on my rom these last few days.
Since then, I can't access my phone, and I can't even access my /data partition from CWM. I've read some threads about some similar issues on this forum but mostly for the Captivate phone, and rarely for the Galaxy nexus. A solution would be to use one SDCard as a /data partition, but since the Galaxy Nexus seems to lacks such interface, I'm quite stuck.
If someone as an idea how to be able to mount again my /data partition in CWM, I would be able to wipe and re-install everything.
I was running the rom Paranoid Android 1.4 with CWM 6.0 on a GSM Galaxy Nexus bought in Switzerland.
Thanks in advance for your help
Julien
I've been able to return back to the stock rom (Jelly Bean) following this guide: http://forum.xda-developers.com/showthread.php?t=1366806
Still don't know what happened and I lost all my datas, but at least the phone is workin' now.
Related
EDIT: I believe I have figured out a part of the problem or all of it, but need some help. In twrp, my good gnex doesn't say "E: unable to mount '/efs' (tw_mount)" while my other phone does multiple times when flashing things. I am having some trouble finding out what this means, but hoping someone can help me figure out what it means and why it is happening so I can solve the problem.
Okay, so I recently got a verizon galaxy nexus, after having had a htc g1, samsung intercept, droid 2 global, htc thunderbolt, and samsung stratosphere. I am not new to rooting and romming and such and have never had any major issues with such things. However the galaxy nexus I got has been giving me a very hard time. I have tried restoring to stock, reunlocking, rooting, and such, and then trying to install roms with twrp and/or cwm recovery. neither one seems to work right on this phone. I tried codename android 3.3.0, bamfed paradigm 2.2, and some other roms. They all get stuck at the boot animation and just stay there, even waiting 5-10 mins does nothing.
The strange thing is that I ordered a 2nd galaxy nexus and so now I have 2, and the 2nd one I just got, and tried to install codename android and it went flawlessly. I unlocked the bootloader, rooted, flashed twrp, backed up, cleared the phone out, and then flashed the JB bootloader, imyoseon's lean kernel, codename android, and cna's gapps package. Doing them all at once, then wiped cache & dalvik after and rebooted. All went perfectly.
Did the same on the first gnex, and it is still on the boot animation. It seems to refuse to boot. I just don't get it. This phone has rejected every rom I give it except for cm9 rc2 and the version of aokp that it originally came with. I literally followed the exact same steps as the other gnex, and not seeing the same results. I don't see how it is possible for a phone to reject random roms like this since it does work in general.
The only difference between the two phones is that one is hardware version 9 and the other is version 10. That and the problem one was running cm9 and had the jb bootloader on it prior to my reflashing the jb bootloader and then the same kernel, rom, and gapps. I would not expect the bootloader to be able to affect anything though, and they had the same one flashed, and system and everything else got wiped, so I don't think being on a custom rom should be affecting this either.
So does anyone have any ideas?
I am having the exact same problem as you are with hardware version 9. I believe it has something to do with the efs partition as well.
ben7337 said:
EDIT: I believe I have figured out a part of the problem or all of it, but need some help. In twrp, my good gnex doesn't say "E: unable to mount '/efs' (tw_mount)" while my other phone does multiple times when flashing things. I am having some trouble finding out what this means, but hoping someone can help me figure out what it means and why it is happening so I can solve the problem.
Okay, so I recently got a verizon galaxy nexus, after having had a htc g1, samsung intercept, droid 2 global, htc thunderbolt, and samsung stratosphere. I am not new to rooting and romming and such and have never had any major issues with such things. However the galaxy nexus I got has been giving me a very hard time. I have tried restoring to stock, reunlocking, rooting, and such, and then trying to install roms with twrp and/or cwm recovery. neither one seems to work right on this phone. I tried codename android 3.3.0, bamfed paradigm 2.2, and some other roms. They all get stuck at the boot animation and just stay there, even waiting 5-10 mins does nothing.
The strange thing is that I ordered a 2nd galaxy nexus and so now I have 2, and the 2nd one I just got, and tried to install codename android and it went flawlessly. I unlocked the bootloader, rooted, flashed twrp, backed up, cleared the phone out, and then flashed the JB bootloader, imyoseon's lean kernel, codename android, and cna's gapps package. Doing them all at once, then wiped cache & dalvik after and rebooted. All went perfectly.
Did the same on the first gnex, and it is still on the boot animation. It seems to refuse to boot. I just don't get it. This phone has rejected every rom I give it except for cm9 rc2 and the version of aokp that it originally came with. I literally followed the exact same steps as the other gnex, and not seeing the same results. I don't see how it is possible for a phone to reject random roms like this since it does work in general.
The only difference between the two phones is that one is hardware version 9 and the other is version 10. That and the problem one was running cm9 and had the jb bootloader on it prior to my reflashing the jb bootloader and then the same kernel, rom, and gapps. I would not expect the bootloader to be able to affect anything though, and they had the same one flashed, and system and everything else got wiped, so I don't think being on a custom rom should be affecting this either.
So does anyone have any ideas?
Click to expand...
Click to collapse
Have you tried flashing stock JB to the hw version 9 one? Handy guide here: http://forum.xda-developers.com/showthread.php?t=1626895
ben7337 said:
EDIT: I believe I have figured out a part of the problem or all of it, but need some help. In twrp, my good gnex doesn't say "E: unable to mount '/efs' (tw_mount)" while my other phone does multiple times when flashing things. I am having some trouble finding out what this means, but hoping someone can help me figure out what it means and why it is happening so I can solve the problem.
Okay, so I recently got a verizon galaxy nexus, after having had a htc g1, samsung intercept, droid 2 global, htc thunderbolt, and samsung stratosphere. I am not new to rooting and romming and such and have never had any major issues with such things. However the galaxy nexus I got has been giving me a very hard time. I have tried restoring to stock, reunlocking, rooting, and such, and then trying to install roms with twrp and/or cwm recovery. neither one seems to work right on this phone. I tried codename android 3.3.0, bamfed paradigm 2.2, and some other roms. They all get stuck at the boot animation and just stay there, even waiting 5-10 mins does nothing.
The strange thing is that I ordered a 2nd galaxy nexus and so now I have 2, and the 2nd one I just got, and tried to install codename android and it went flawlessly. I unlocked the bootloader, rooted, flashed twrp, backed up, cleared the phone out, and then flashed the JB bootloader, imyoseon's lean kernel, codename android, and cna's gapps package. Doing them all at once, then wiped cache & dalvik after and rebooted. All went perfectly.
Did the same on the first gnex, and it is still on the boot animation. It seems to refuse to boot. I just don't get it. This phone has rejected every rom I give it except for cm9 rc2 and the version of aokp that it originally came with. I literally followed the exact same steps as the other gnex, and not seeing the same results. I don't see how it is possible for a phone to reject random roms like this since it does work in general.
The only difference between the two phones is that one is hardware version 9 and the other is version 10. That and the problem one was running cm9 and had the jb bootloader on it prior to my reflashing the jb bootloader and then the same kernel, rom, and gapps. I would not expect the bootloader to be able to affect anything though, and they had the same one flashed, and system and everything else got wiped, so I don't think being on a custom rom should be affecting this either.
So does anyone have any ideas?
Click to expand...
Click to collapse
Looks like you created swap and other strange partitions with a recovery, so "sdcard" hyerarchy got corrupted
try to lock and unlock device
in your adb folder type those commands
fastboot oem lock
then
fastboot oem unlock
Hi everybody, I'm new in this forum and I'm sorry if my english won't be the best you will read
Here's my problem:
I used to have problems with my GN stock with 4.2.2 because of the issue that makes it slower when the Internal storage get almost full (even if there were still some GBs free). After that it started having the reboot issue, so I decided to do the factory reset. After some of these full wipe I decided to unlock the phone and root it to install a custom ROM (paranoid 3+) to have the possibility to save my data if necessary. After 2 weeks the phone starts rebooting suddenly very often, in particular when the internet connection (WIFI or mobile data) was on.
Today I finally decided to do a backup with titanium backup and restore my phone. I used Nexus Root Toolkit to flash stock 4.2.2 downloaded from google's developers site. It worked but, as it's written in the main interface of the progam, I lost my root permissions so I repeated the root procedure, but it didn't worked. Every time I try to obtain them (I tried with the adb method and with Nexus Root Toolkit) doesn't show errors, but when I check for root access, for example using root checker, the message displayed is always "The phone doesn't has root permissions".
Now, what is my problem? I used to have an Acer Liquid months ago and with it I used to do an Hard Reset and install all over again, can I do it with my GN too? Please help me, because I'm going crazy
Hi guys,
I had already suffered in the past for sudden reboots, but at least i was able to use the phone for a decent amount of time and fix it. After last night, though, the situation seems desperate. When i woke up i was able to turn off the alarm clock, check my email, but then hell started...
My phone is a gsm Nexus (maguro i9250), with CyanogenMod11 snapshot M5 and the appropriate google apps (at least they were appropriate about 1 month ago). I recently had some minor issue with the Google+ app, after it was updated: it kept crashing, until i uninstalled it and reinstalled after downloading from the Play Store. Should i instead search for a newer gapps packet?
Now the situation is pretty awful. The phone will reboot after at most 2 minutes. I don't really know what makes it crash so bad.
I also have two weird problems. Whatever change i manage to make before the phone reboots doesn't get persisted. For example, the alarm clock will always start activated, no matter if i managed to deactivate it before the reboot.
I'm also not able to reset it to factory defaults. I am using ClockworkMod 6.0.4.7. If i try the reset procedure, the /data and /cache partitions are formatted, but not the sdcard one. Indeed, i get the following output:
Code:
Formatting /data
Formatting /cache
Formatting /sd-ext
E: unknown volume for path [/sd-ext]
Formatting /sdcard/.android_secure
Data wipe complete
When i reboot the phone after this procedure, everything is still there, and the phone will keep doing its reboots after 1-2 minutes.
What can i do? Is there an hardware way to hard-reset the phone? Is there a program i could use?
Thanks in advance!
Fried EMMC (memory)
Sent from my Galaxy Nexus using XDA Free mobile app
mrgnex said:
Fried EMMC (memory)
Click to expand...
Click to collapse
Maybe, but if everything is still there after a reboot, sounds doubtful.
Have you tried installing a different rom? Can you connect via adb? Do you have a nandroid?
Format /system under Mounts and Storage in CWM and reflash ROM and GApps?
Hi guys, thanks for your replies! Sorry for the late answer, i was pretty busy.
I spent last night trying everything i could, but i think my phone is gone
I used Skipsoft's Android Toolkit and Odin, with no success.
The first one seemed to succeed: i tried twice, with two different stock roms, but i always ended up with the same CM11, same apps, same everything.
Odin always failed (i tried at least 3 times, i honestly lost the count).
I did find a post in the forums regarding a guy with my same problem, and he was told about the eMMC as well. I am pretty sure that is my problem as well.
Further proofs of that:
1) I downloaded the latest CM11 nightly build, was able to push its zip file on the device using Eclipse (i swear it was there), but when i tried to flash it using CWM, the file wasn't there.....
2) With Android Toolkit i was able to boot into a different recovery tool (TWM, i think). I wiped everything with it, and i was starting to hope.... but the same darn CM11 appeared!
I don't have a nandroid, i formatted everything i could in Mounts in CWM (i got to a point that i formatted everything that was formattable). I also tried to reflash the rom and gapps. No luck, always ended up with the same situation.
I didn't really try a different rom. I didn't try to connect using adb on the terminal, but i think that Eclipse is based on that, so i think adb is working.
Oh well... Right now i'm using an old phone, but i have started looking for a new one, i am tempted by the Nexus 5
frabena said:
Hi guys, thanks for your replies! Sorry for the late answer, i was pretty busy.
I spent last night trying everything i could, but i think my phone is gone
I used Skipsoft's Android Toolkit and Odin, with no success.
The first one seemed to succeed: i tried twice, with two different stock roms, but i always ended up with the same CM11, same apps, same everything.
Odin always failed (i tried at least 3 times, i honestly lost the count).
I did find a post in the forums regarding a guy with my same problem, and he was told about the eMMC as well. I am pretty sure that is my problem as well.
Further proofs of that:
1) I downloaded the latest CM11 nightly build, was able to push its zip file on the device using Eclipse (i swear it was there), but when i tried to flash it using CWM, the file wasn't there.....
2) With Android Toolkit i was able to boot into a different recovery tool (TWM, i think). I wiped everything with it, and i was starting to hope.... but the same darn CM11 appeared!
I don't have a nandroid, i formatted everything i could in Mounts in CWM (i got to a point that i formatted everything that was formattable). I also tried to reflash the rom and gapps. No luck, always ended up with the same situation.
I didn't really try a different rom. I didn't try to connect using adb on the terminal, but i think that Eclipse is based on that, so i think adb is working.
Oh well... Right now i'm using an old phone, but i have started looking for a new one, i am tempted by the Nexus 5
Click to expand...
Click to collapse
You can try by downloading a clean google factory image and then flash it using bootloader and see it helps, it could be a bad script inside. If this doesn't help then you should totally get the Nexus 5. I got GNex only recently and its still a good device I reassure you. A little tweak and a little overclock makes it as good as a stock N4 minus the bad graphics.
frabena said:
Hi guys, thanks for your replies! Sorry for the late answer, i was pretty busy.
I spent last night trying everything i could, but i think my phone is gone
I used Skipsoft's Android Toolkit and Odin, with no success.
The first one seemed to succeed: i tried twice, with two different stock roms, but i always ended up with the same CM11, same apps, same everything.
Odin always failed (i tried at least 3 times, i honestly lost the count).
I did find a post in the forums regarding a guy with my same problem, and he was told about the eMMC as well. I am pretty sure that is my problem as well.
Further proofs of that:
1) I downloaded the latest CM11 nightly build, was able to push its zip file on the device using Eclipse (i swear it was there), but when i tried to flash it using CWM, the file wasn't there.....
2) With Android Toolkit i was able to boot into a different recovery tool (TWM, i think). I wiped everything with it, and i was starting to hope.... but the same darn CM11 appeared!
I don't have a nandroid, i formatted everything i could in Mounts in CWM (i got to a point that i formatted everything that was formattable). I also tried to reflash the rom and gapps. No luck, always ended up with the same situation.
I didn't really try a different rom. I didn't try to connect using adb on the terminal, but i think that Eclipse is based on that, so i think adb is working.
Oh well... Right now i'm using an old phone, but i have started looking for a new one, i am tempted by the Nexus 5
Click to expand...
Click to collapse
Well I got bad news well not really bad but kinda. If you wiped efs data while you were wiping your phone will never properly connect to the network anymore. That obviously won't matter unless you somehow get out of this bootloop.
First of all, hi @ all
Today I rooted my Tablet sucesfully using Odin3 with CF-Auto-Root-lt03lte-lt03ltexx-smp605.tar.md5
After this I tryed to backup all important stuff using TWRP so in case that flashing CM fails I could return to android without problems.
Becourse of a problem with the newest twrp message I got an information that the backup is going to be safed on the intern memmory (so I later would have to move it manually to the externSD card). Well that did not sound like a problem so I started the backup function, it bootet in the recovery mode.
Well I expected it to run automaticly after choosing wich partitions it should backup so I did not knew what to choose in the menu and decided to reboot wondering if I missed some explenation.
It looks like that was a bad idea, after the Samsung logo I just get a blackscreen and dozens of messages that xzy was terminated. Rebooting doesnt help.
So ironicly I crashed my device while trying to backup
At least I have absolut 0 personal data on it so I lost at least nothing.
Now my Questions:
A)To return to use my device again with android I can still use this? sammobile.com/firmwares/download/40784/P605XXUCNL1_P605BTUCNL2_BTU.zip
And is there somewhere a faster download?
Or is there a chance that after wipe data/factory reset I can use it again?
B) If I get techsoncall.wordpress.com/2015/03/30/installing-cyanogenmod-on-galaxy-note-10-1-2014 this right I actualy could just clear now the entire intern memory of my tablet, cpy the Cyanogenmod (and may gaps) on the sdcard and flash then install it to get my tablet running CM?
I would admire every comment, Im going to fly in few days so I'm actually a little bit stressed course of this fail
Well a hardreset helped but the problem was that I just installed the TWRP app and did not install the recovery mod with this app.
After doing that everything runs fine.
Hello all! I've got a puzzling issue (for me, at least) that I'd like to see if anyone else has encountered and what their possible fix might be.
So I've been alternating between running Resurrection Remix and Pure Nexus the past few months and have had no issues flashing new builds or kernels. Last night when I went to switch back from RR to Pure Nexus I encountered and error I haven't seen before and some weird results from it.
When I went to flash the Pure Nexus it kept failing stating TWRP was unable to find the meta/inf/com/Google (I think) data in the zip. I tried flashing RR again with the same issue. I then tried to wipe and restore a TWRP backup that didn't end up working even though it said it did. I then decided screw it and flashed the factory image for the Pixel XL and was able to at least get booted and running on stock. However, my storage is pretty much gone and now only have like 6gb out of 8gb total. Upon I spection System is currently taking up 20gb worth of storage and even after flashing the factory image again it is still not resolved.
Can anyone tell me what I managed to do here and if there is a fix? Realistically I'd love to figure out how to actually repartition everything in the phone and start from scratch again.
Any advice or insight would be greatly appreciated as I'm not new to rooting and rom'ing but am getting uinely confused as to what has happened here.
PS: I attached a picture of my storage breakdown but can't inspect further due to not having root and being on stock. Viewing storage in TWRP didn't yield much more I formation either.
MR H3LLMAN said:
Hello all! I've got a puzzling issue (for me, at least) that I'd like to see if anyone else has encountered and what their possible fix might be.
So I've been alternating between running Resurrection Remix and Pure Nexus the past few months and have had no issues flashing new builds or kernels. Last night when I went to switch back from RR to Pure Nexus I encountered and error I haven't seen before and some weird results from it.
When I went to flash the Pure Nexus it kept failing stating TWRP was unable to find the meta/inf/com/Google (I think) data in the zip. I tried flashing RR again with the same issue. I then tried to wipe and restore a TWRP backup that didn't end up working even though it said it did. I then decided screw it and flashed the factory image for the Pixel XL and was able to at least get booted and running on stock. However, my storage is pretty much gone and now only have like 6gb out of 8gb total. Upon I spection System is currently taking up 20gb worth of storage and even after flashing the factory image again it is still not resolved.
Can anyone tell me what I managed to do here and if there is a fix? Realistically I'd love to figure out how to actually repartition everything in the phone and start from scratch again.
Any advice or insight would be greatly appreciated as I'm not new to rooting and rom'ing but am getting uinely confused as to what has happened here.
PS: I attached a picture of my storage breakdown but can't inspect further due to not having root and being on stock. Viewing storage in TWRP didn't yield much more I formation either.
Click to expand...
Click to collapse
Format userdata should fix it.
toknitup420 said:
Format userdata should fix it.
Click to expand...
Click to collapse
I believe I tried that at one point last night but will try it again here shortly. Any thoughts on what it could be if this does not fix it? And what method would you recommend to format userdata? Do I do it through TWRP?
fastboot format userdata
swapavi said:
fastboot format userdata
Click to expand...
Click to collapse
So this did indeed fix my storage partition issues but now I am unable to flash TWRP to my device. It is stating my recovery partition doesn't exist. What the hell is happening? haha
MR H3LLMAN said:
So this did indeed fix my storage partition issues but now I am unable to flash TWRP to my device. It is stating my recovery partition doesn't exist. What the hell is happening? haha
Click to expand...
Click to collapse
You may need to fast boot new boot images to slot a and b. You just have to unzip factory image and you will see them in there. Or just flash the factory image all over. Start fresh.
MR H3LLMAN said:
So this did indeed fix my storage partition issues but now I am unable to flash TWRP to my device. It is stating my recovery partition doesn't exist. What the hell is happening? haha
Click to expand...
Click to collapse
Don't flash recovery, you're pixel will get all screwed up lol. You temp boot it and install via the twrp installer zip.