[Q] Problem trying to install CyanogenMod - Encrypted device - ICS 4.0.4 - RAZR HD Q&A, Help & Troubleshooting

Hi to all. First of all, sorry for my bad english as english is not my native language. I have a rooted ICS stock Android 4.0.4 running on Motorola Razr HD (XT925) (Argentina - Personal). Bootloader unlocked and Custom Recovery installed with no problems. I had full encryption on /sdcard and /data, too.
The problems begins when I try to install CyanogenMod, as Custom Recovery (and TWRP) cannot mount or format /sdcard and /data.
The ROM's anyways installs OK, but the problems begins when the different versions of CyanogenMod try to boot. This is what happened with the versions I tried (I was putting the .zip rom and gapps files on an external sd that is not encrypted (external_sd) ):
cm-10.1-20130723-UNOFFICIAL-epinter-xt925 (Android 4.2)
Installation from Custom Recovery ok. This version skips asking for the internal storage password, and is the only version that works. But the wifi on this version doesn't work and my internal storage is not accesible.
cm-10-20130421-UNOFFICIAL-epinter-xt925 (Android 4.1)
Installation from Custom Recovery ok. This version asks for the internal storage password at boot, but the keyboard crash when I try to type it (so I cannot finish the configuration).
cm-10.2-20130820-UNOFFICIAL-epinter-xt925 (Android 4.3)
Installation from Custom Recovery ok. This version asks for the internal storage password at boot and the keyboard works, but then the CyanogenMod boot logo appears and continue in an infinite loop (so I cannot finish the configuration).
Liquid-JB-v2.9-08142013-xt925 (Android 4.2) (not a CyanogenMod ROM but I tried it anyways)
Installation from Custom Recovery ok. This version doesn't even boot, I turn on the phone (the "M" logo appears) and stays there forever.
The only temporary solution that I'm on right now was to restore the stock rom (I made a backup with Custom Recovery).
It pretty seems that the root of these problems is that the device is encrypted, so the solution would be to "unencrypt" the partitions and format all the data that are there (I made a backup of the internal storage too, so I dont mind of loosing that data); but I searched the whole internet and couldn't find an answer that work. I tried doing a factory reset from the original ROM (Settings - Privacy Settings...) (didn't worked, because it tries to load the stock recovery and now I'm on Custom Recovery), tried using TWRP (some sites says it is capable to handle encrypted devices, but does the exact same that Custom Recovery does, it cannot format or mount /sdcard and /data, and never ask for my password), etc etc ...
Any ideas to format the internal storage or install a ROM that works well with encrypted storage? Any more information you need, I will be glad to tell you.
Thanks to all!

Related

Encrypted tablets - updates?

Lo all
I've encrypted my Xoom (running 4.0.3 ICS, US Mot std image on a UK WiFi Xoom). All is working, and I have the CWM recovery installed.
In CWM I can mount & access /system, but not /data - so I presume that's what's encrypted.
Are CWM flashable zips still going to work, presuming they don't (try to) touch /data?
Also - does Nandroid backup get screwed by the encrypted partition, or does it run a raw dd?
Anybody? Bueller?
I just tried an update to ICS on my encrypted xoom and had no luck. It consistently would stick at the EOS boot animation. You are correct that the problem is the /data partition is encrypted. It cannot be mounted in CWM for wiping the dalvik cache or writing any update information.
I did get the password entry screen before the EOS boot animation would start, and could then connect to the xoom with adb and get a shell. Attempting to delete dalvik-cache from the shell and reboot did not give any better results. It seems like there should be some way to make it work, but I finally gave up and did a 'fastboot erase userdata' to wipe the encrypted /data partition. I was able to reboot into CWM, wipe data, cache, and dalvik cache, flash the EOS and GApps zips and get back up successfully. Tablet is not encrypted now and I had to restore all my data files from a backup I had ftp'd to my desktop beforehand. In hindsight I probably should have unencrypted the tablet before flashing, but I have seen several posts indicating that unencrypting did not work properly.
You can't decrypt, it's basically a "factory restore".
Just found CWM can't back it up via nandroid too. Interesting :\
I installed ICS build #44 on my Xoom then encrypted it about a week ago. I just updated to Team EOS 1.0.0 build and updated GAPPS. Everything works.

[Q] TF101 Installing Custom ROM on Encrypted device

I recently managed to successfully root my TF101.
I installed CWM (Via ROM Manager) and downloaded CM9
I boot into CWM and attempt to do a nandroid...can't find path.
I attempt to just install from SDCard...can't find path
Realization (and research) hits that CWM can't see the external sd, and the system doesn't see it as SDCARD but EXT-.
CWM can't see the internal SDCard because apparently on the Tablet the ICS encryption locks that down (but doesn't on my EVO since the SC Card isn't part of the internal storage)
I attempt to perform a factory data wipe to clear out the encrtyption , but upon reboot CWM loads. I try to perform the boot-launcher data wipe, but then CWM loads.
I try to use CWM to factory reset but since it can see the damned SDCard because of the encryption, no dice.
My machine is not bricked, as I can still boot into the previous install but I can't seem unable to format the thing to install CM9.
What to do, and thanks.
It has been said multiple times before DO NOT USE ROM MANAGER.
Either use Thing O Doom's peri to install a different CWM or Gnufabio's Recovery installer or NVFlash a rom to completely wipe. And don't use encryption there is no point 99% of the time
I didn't check here first, which is obviously what was my first mistake.
Will any of those recoveries be able to access and format the SD Card area?
Also, I use encryption as I do have sensitive things on my machine that I don't want exposed in case the machine is stolen. First time I've ever had it give me a problem, as the phone encrypts differently.
Team roug's recovery has internal and external sd support and i think the encryption is an ics/tegra 2 bug more than anything
Ok, so I managed to get the new recovery on via Thing O Doom's peri. And I was able to install Revolver via the ext card...but upon boot I was prompted for my encryption pin and got the message that android was updating...My Build number is now Revolver but everything is the same as it was. I still can't factory wipe this damned thing.
Upon request to wipe, it boots back to recovery and says formatting data and cache, data wipe failed.
Tis site states http ://0xfeedface.org/blog/lattera/2012-06-04/installing-cm9-encrypted- android-tablet
The dilemma
When you encrypt your Android device, the /data partition is what gets encrypted. The partition in full is encrypted and cannot be mounted within CWM. CWM also cannot perform a wipe, since it cannot mount the /data partition. And CWM cannot mount the external SD card. This is our dilemma. No access to the internal SD. No access to the external SD. No way to perform a wipe and format the internal SD from CWM.
The Solution
What we need to do, then, is use adb while the tablet is in recovery mode to reformat the internal SD card, thereby removing the encryption. On the US Transformer Prime, the internal SD card is at /dev/block/mmcblk0p8. The partition for our spare SD card will be at /dev/block/mmcblk1p1. You will need to replace those device entries for any other device you might attempt this on. After formatting the internal SD card, we will mount it and then mount the external SD card at /data/media:
In CWM, wipe cache
adb shell
mke2fs -t ext4 /dev/block/mmcblk0p8 # Warning: This can take a while. Be patient.
mount /data
mount /dev/block/mmcblk1p1 /data/media
Now go back to CWM on your device, then go ahead and flash your CM9 and gapps zips like normal. You now have CM9 installed! The /data partition is not encrypted. If you do not need to flash any other ROMs (unlikely if you're reading this article), feel free to re-encrypt your device.
Click to expand...
Click to collapse
I don't know the block numbers for the TF01
you need to undo the encryption before you can wipe anything
You can't. Hence my problem. I cannot mount,delete, or format the SDCard. It sounds like the process in the above post is the solution, but I don't know how to find out what block numbers the tf101 uses.
If you don't mine losing your data NVflashing a rom will resolve all the problems
Yep nvflash will do the trick otherwise as the solution you found yourself explains
Use adb in recovery ( in other words hook it up on a pc ) for this you will need android sdk runnin on your pc
More info about adb u can find here
http://forum.xda-developers.com/showthread.php?t=1751439&highlight=adb+help
Good luck
Thanks to all, I have resolved my issue!
I had to download the stock rom, extract the blob, and use Wheelie for PC to NVFlash everthing abck to stock. I was then able to update over OTA, and use the excellent Thing O Doom's peri to re-root and flash the working recovery.
There should be several items in the Root FAQ up top, such as:
If you are encrypted and going to root, factory reset to get rid of the encryption FIRST since the encryption locks down the SDCARD partition (Unlike on the phone)and none of the recoveries can access it to mount. DON"T use ROM manage on the TF101 and always, always check XDA first.
:good:
darthrater said:
Thanks to all, I have resolved my issue!
I had to download the stock rom, extract the blob, and use Wheelie for PC to NVFlash everthing abck to stock. I was then able to update over OTA, and use the excellent Thing O Doom's peri to re-root and flash the working recovery.
There should be several items in the Root FAQ up top, such as:
If you are encrypted and going to root, factory reset to get rid of the encryption FIRST since the encryption locks down the SDCARD partition (Unlike on the phone)and none of the recoveries can access it to mount. DON"T use ROM manage on the TF101 and always, always check XDA first.
:good:
Click to expand...
Click to collapse
That FAQ is sadly pretty outdated, I wish I could liberate the OP
Glad all is working now though.

(SOLVED) [Q] [HELP] Motorola NOOB! Mount point information for XT925?

Hi there, I seem to have messed up my mounting partitions while trying to deodex Stock JB Central Europe. I basically used xultimate to pull the files and deodex then tried using adb shell to mount the system partition and copy them over. After I rebooted the phone, it would get stuck on unlocked bootloader warning or on the motorola logo. I hard reset into recovery and restored a nandroid backup and once booted into android found so many folders under the Storage folder such as "asec", "obb", rfs0" and so on. Now, when I try to wipe dalvik-cache in recovery, i get the following error: "E: unknown volume for path [/sd-ext]". Also, when i try flashing custom rom's and reboot, it gets stuck on the unlocked bootloader warning and wont load - while in recovery after flashing, i also get another error something like this: "E: cant load /cache/recovery.log" or similar. I also sometimes have issues mounting system, cache partitions, data and internal storage, all depending on which custom recovery i am using. I read on another site that downgrading to ics might solve mounting problems so I forced a downgrade to ics but that didnt work either and am still on ics.
Is there a way to restore the partitions correctly or are they stuck this way? Would mounting and remounting solve this problem? Any help would be much appreciated and would very much appreciate it if someone could upload their mount point info so i could use to try and fix it.
Many thanks in advance.
EDIT: Managed to flash Slim Bean 4.3 Official using OUDHS recovery without wiping cache and dalvik-cache at first. After reboot, it would bootloop so went to recovery and wiped cache and dalvik-cache then it worked. Still no sd-ext and some apps can't write or backup to external memory such as Go Backup & Restore Pro so what remains is to mount/unmount the partitions correctly.

[Completed] [Q] My system,data, preload,internal storage or external storage won't mount

I accidentally formatted and unmounted my system on my N7000 in CWM v6 .0 .5 .0 but i can still access my external storage in installing a zip somehow. I recently successfully installed Lollipop beta 5.0.1 cyanogen based on my Note but then i wanted to go back to slim wizz rom because i missed that tablet feature . After re-installing the slimwizz tablet rom i accidentally formatted and unmounted my system and the slim wizz doesn't boot up. When i turn my phone on it boot loops from the lollipop animation and stays as such. Before i did the Slimwizz i used twrp - installed the kernel for slim wizz , rebooted and from CWM i flashed the Slimwizz then somehow while formatting cache, data and internal storage (cause i really didn't have anything in there anyways) i accidentally unmounted my system in process
What can be done to re-mount my system, various storages and data back? Also i can still access TWRP by installing the kernel zip from my sd card but its not much help since my loads are still unmounted in TWRP
busawahk said:
I accidentally formatted and unmounted my system on my N7000 in CWM v6 .0 .5 .0 but i can still access my external storage in installing a zip somehow. I recently successfully installed Lollipop beta 5.0.1 cyanogen based on my Note but then i wanted to go back to slim wizz rom because i missed that tablet feature . After re-installing the slimwizz tablet rom i accidentally formatted and unmounted my system and the slim wizz doesn't boot up. When i turn my phone on it boot loops from the lollipop animation and stays as such. Before i did the Slimwizz i used twrp - installed the kernel for slim wizz , rebooted and from CWM i flashed the Slimwizz then somehow while formatting cache, data and internal storage (cause i really didn't have anything in there anyways) i accidentally unmounted my system in process
What can be done to re-mount my system, various storages and data back? Also i can still access TWRP by installing the kernel zip from my sd card but its not much help since my loads are still unmounted in TWRP
Click to expand...
Click to collapse
Hi. Thank you for using XDA Assist. I'm confident you'll find answers to your query here: http://forum.xda-developers.com/galaxy-note/help
Do remember to backup all data before modifying anything major on your phone. Good luck.

[A510] Can't mount /data on any recovery

Hi,
I wanted to reset my 510 to a fresh 4.4.4 install. So I decided to "restore to factory settings" within the android system settings menu.
kitkat CM12 4.4.4 by shreps was working fine before, I just wanted to get rid of the data in order to give the tablet away.
now I'm stuck with a soft bricked device, it seems:
- when starting the tablet, the CM screen shows, but freezes after a while
- flashing any CM version in CWM 6..0.5 by shreps shows a "error: can't mount /data"
- wipe cache / data shows the same error
- wipe dalvik cache doesn't seem to respond in any way
- I reflashed CWM 6.0.5 using fastboot flash recovery, but to no success..
what options do I have now? can I format and remount the /data partition via ADB? do I need to go to stock?if, so, how?
Thanks for your ideas!
ok, via
fastboot -w -v
i could reformat the data partition somehow.
I still got an
E:unknown volume for path [/sd-ext]
error, but it continued and works for now.
huedrant said:
ok, via
fastboot -w -v
i could reformat the data partition somehow.
I still got an
E:unknown volume for path [/sd-ext]
error, but it continued and works for now.
Click to expand...
Click to collapse
Glad you dot it going.
I just pulled my 701 out of retirement (broke my Sony z2 screen trying to change my battery) so taking a look in here.
The data format has always been a bit twitchy, but I run the latest version of TWRP for KK. I remember bricking my original Data partition wiping it because some bozo used the wrong partition info making the original recovery for JB. Exchanged the tab.
I recall the bootloader version had to match what version of the ROM you installed (JB, KK, etc), and maybe the recovery also (can't remember). Latest TWRP for KK seems to work for me as I installed Pac Rom before I retired it. TWRP Ver 2.7.1.0
As with the "Path to ext SD", that's always been there if I recall. Just means you have to install a ROM from internal memory. Although my TWRP seems to mount it fine.
But I will say, feels like I've entered the dark ages again.

Categories

Resources