Related
Hello,
i have just installed the official stock ICS 4.0.3 Rom to my Nexus S and everything was really fine... until i tried to root it. As someone who tries to take security seriously, i immediately encrypted the device using the tools provided by ics (works ok).
but unfortunatly it's now not possible anymore to mount /sdcard while in recovery, which makes rooting and installing updates impossible (or is there any other way? eg. fastboot?).
therefore my question: will clockworkmod recovery support ics encrypted devices in the (near) future? i know its gonna be a p.i.a. to type a password with only the volume buttons, but hey
i like the encryption and would like to keep it, but not beeing able to use recovery like before is a big drawback...
greetings
Georg
Same for me.
Hope to see encryption support in clockworkmod soon.
I bought Rom manager premium even if I never flash from rm just to support the developers... hope they will be able to get it sorted out
Op -- I'm interested in this for when my phone (EVO 3D) finally gets ICS. Will you post an update to this thread if you hear anything?
BTW, with TWRP getting touchscreen support, it can't be too much longer before CWM gets touchscreen since I think the guys in TWRP were going to start contributing to CWM, from what I've heard anyway. So that would solve the password typing problem.
Georg, thanks for asking this question as I've been wondering the same exact thing. Hopefully we'll get a good answer soon.
Alternatives for ClockworkMod Recovery
I encrypted my device (the Exchange account I added required it) n... now I cant do anything in recovery ... it wont mount the drive ... any suggestions for a replacement ...
thanks ...
mrosensweig said:
I encrypted my device (the Exchange account I added required it) n... now I cant do anything in recovery ... it wont mount the drive ... any suggestions for a replacement ...
thanks ...
Click to expand...
Click to collapse
Its because the way encryption works you have to boot and enter code, that's the whole point, no recovery can do it atm
Sent from my ice cream powered Nexus S
small update:
nothing new on the subject, but i didnt check out the new touch recovery (anyone tried it yet?).
in the mean time i went back to an unencrypted CM9...
I didn't read anything about encryption so did not upgraded to the touch recovery yet
you should lock the bootloader if someone is nagging you
jomir said:
small update:
nothing new on the subject, but i didnt check out the new touch recovery (anyone tried it yet?).
in the mean time i went back to an unencrypted CM9...
Click to expand...
Click to collapse
Jomir, what was the procedure you used to get back to CM9? Is it possible to repartition, erasing the encrypted partitions so a new rom can be flashed? How?
Thx,
rmsilva
rmsilva123 said:
Jomir, what was the procedure you used to get back to CM9? Is it possible to repartition, erasing the encrypted partitions so a new rom can be flashed? How?
Thx,
rmsilva
Click to expand...
Click to collapse
Restore a backup or do a clean install(format boot, system, cache and data)
Sent from my ice cream powered Nexus S
DarkhShadow said:
Restore a backup or do a clean install(format boot, system, cache and data)
Sent from my ice cream powered Nexus S
Click to expand...
Click to collapse
Thanks for the reply, DarkhShadow. The problem is that CWM can't wipe or format these partitions, since it can't mount /sdcard (which is encrypted). If I could only access the external sdcard from within CWM, I could just wipe everything and then install a new rom. But since it can't mount /sdcard, I can't access sd-ext. nvflash is not an option, since my TF101 is B90. Is there a way to either restore the stock recovery (overwrite CWM) or boot from the external SD so I can run a script such as "super wipe full" (http://forum.xda-developers.com/showthread.php?t=1245892)? Maybe there's a way to run the wipe script through adb? If I can just format the partitions (which is what the script does), then CWM would be able to mount /sdcard and, consequently, the external SD and I can flash a new rom (such as revolution HD 3.0.1).
Thanks,
rmsilva
Honestly idk then, try a factory reset on phone(ie booted up) and then maybe it will be unencrypted?
Sent from my ice cream powered Nexus S
The funny thing is that stock recovery on an encrypted phone can write to the disk, but only from a warm reboot (perhaps the kernel stays resident?).
When I say write to disk I say apply the leaked OTA update, 4.0.4 for the VZ Gnex. And correct me if I am wrong, it's writing and mounting the disk, no?
Anyhow, this is done from stock recovery which is open source. So you ask yourself, why can't Koush support mounting the disk from a warm recovery state reboot? Maybe he doesn't know this?
DarkhShadow said:
Its because the way encryption works you have to boot and enter code, that's the whole point, no recovery can do it atm
Sent from my ice cream powered Nexus S
Click to expand...
Click to collapse
rmsilva123 said:
Jomir, what was the procedure you used to get back to CM9? Is it possible to repartition, erasing the encrypted partitions so a new rom can be flashed? How?
Thx,
rmsilva
Click to expand...
Click to collapse
i did a factory reset (from the settings menu), installed recovery per adb/fastboot and installed cm9 from sdcard in recovery.
Use tmpfs to install a new ROM in crypted system
Hello Everyone
To flash a new ROM you can do as follows:
boot in Recovery
format cache partition
from your PC use adb to mount /sdcard as tmpfs:
adb shell mount -t tmpfs none /sdcard
put your ROM on the (fake) sdcard
adb push <your rom> /sdcard
use the recovery to flesh the ROM as usual
This worked form me.
Sorry to be late...
What about a nandroid backup or restore? How big is /cache?
orcruin said:
Hello Everyone
To flash a new ROM you can do as follows:
boot in Recovery
format cache partition
from your PC use adb to mount /sdcard as tmpfs:
adb shell mount -t tmpfs none /sdcard
put your ROM on the (fake) sdcard
adb push <your rom> /sdcard
use the recovery to flesh the ROM as usual
This worked form me.
Sorry to be late...
Click to expand...
Click to collapse
Sorry I didn't try with a nandroid backup but I think it is too big to fit the device memory...
You can backup data inside the sd partiton (phone up and running, just to don't lose data...), boot into recovery, format sdcard partition, mount it, put the backup in the sdcard and after install the nandroid backup...
I think that it could work but I am not sure. If after formatting the sdcard you can mount it, the task is done. You can put the backup on it using adb push and flash using recovery.
If you try please give me some news.
Regards
orcruin said:
Hello Everyone
To flash a new ROM you can do as follows:
boot in Recovery
format cache partition
from your PC use adb to mount /sdcard as tmpfs:
adb shell mount -t tmpfs none /sdcard
put your ROM on the (fake) sdcard
adb push <your rom> /sdcard
use the recovery to flesh the ROM as usual
This worked form me.
Sorry to be late...
Click to expand...
Click to collapse
I'm kind of a noob when it comes to adb. What is that process doing exactly? How big is the fake sdcard? I want to make sure I understand all the implications before I dive in. Of course I need HTC to release a ICS ROM first. ;-)
thx1200 said:
I'm kind of a noob when it comes to adb. What is that process doing exactly? How big is the fake sdcard? I want to make sure I understand all the implications before I dive in. Of course I need HTC to release a ICS ROM first. ;-)
Click to expand...
Click to collapse
First it formats the cache partition. Then mount the /sdcard so that you can access it from your pc. After you mount the /sdcard, you can put your rom zip into it. After the zip has been transferred into /sdcard, you can flash the zip as usual.
Since nexus s doesn't have sdcard slot, it mounts the internal storage as '/sdcard' to treat it like a sdcard, thus 'fake' sdcard. The 'fake' sdcard is around 13GB.
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.
I am relatively new to the world of rooting and ROMs, but I have successfully installed CM10 on a previous Samsung phone, so I am decently literate.
I am currently attempting to install CM10.1 on my Verizon Galaxy S III (following the instructions on the Install CM for d2vzw page on the CM wiki), but I have reached an impasse at step 7. I was not aware that I had to put the VRALE6.bootloader.zip file on the SD card before starting this process, so I am now attempting to get that file onto my SD card either by sideloading through CWM or by pushing it to the SD card through adb. The issue is that CWM gives me an error (can't mount SD card) and adb doesn't recognize my device (I have tried installing and reinstalling various drivers for the past few hours). I enabled USB Debugging mode before starting the process, but I am only able to get into Download and CWM modes right now (if I don't do the Download Mode or Recovery Mode key combination, I am stuck on the Galaxy S III screen). Am I bricked at this point, or is there a way to get VRALE6.bootloader.zip onto my phone and continue with the ROM process?
It is important to note that I formatted the SD card before starting this process because I wanted enough space to put the Cyanogenmod file on it. However, I think I may have formatted it generically rather than into FAT-32. Could this be the issue?
I am going to pick up a microSD card reader today in order to flash the SD card to FAT-32 and put the CyanogenMod file on it.
I am getting 5 errors upon startup of CWM (E: Can't mount /cache/recovery/command, can't mount /cache/recovery/log, etc.). When I try to mount the SD card or external SD card, I get E: Can't mount /sdcard/
Same issue with sd card not mounting.
I'm having somewhat of the same issue. I've tried both Clockwork recovery and TWRP and have the same issue.
Should have mentioned that i still have access to the stock rom and can use my phone just fine.
I some how got Clockwork mod recovery to work using the Rom Manager pro App.
I wish i had been paying better attention to what i was doing but i know i updated CWMrecovery from in rom manager and chose to install my chosen rom with that.
My suggestion is to start over completely. There is a much easier way to do this.
My suggestion is to flash one of the rooted stock ROMs through Odin. There's a thread in android development that has rooted stock. Then when that's done boot up your phone. If it bootloops wipe data. Then use Ez-Unlock 1.2 app to unlock your bootloader. Make sure it's 1.2. Now use GooManager to flash TWRP. You are done! This is probably the easiest way to do this.
Thread: http://forum.xda-developers.com/showthread.php?p=33948598
Sent from my SCH-I535 using Tapatalk
Sent from my SCH-I535 using Tapatalk
Sandman-007 said:
My suggestion is to start over completely. There is a much easier way to do this.
My suggestion is to flash one of the rooted stock ROMs through Odin. There's a thread in android development that has rooted stock. Then when that's done boot up your phone. If it bootloops wipe data. Then use Ez-Unlock 1.2 app to unlock your bootloader. Make sure it's 1.2. Now use GooManager to flash TWRP. You are done! This is probably the easiest way to do this.
Thread: http://forum.xda-developers.com/showthread.php?p=33948598
Sent from my SCH-I535 using Tapatalk
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I am not familiar with TWRP, so is the process the same for flashing CM (putting CM zip file on sd card and going to install from SD card in TWRP)? Are there any additional steps beyond this?
I am following the directions in the thread linked above to root and install TWRP. So far, I have the rooted stock ROM running fine, but I can't get TWRP to work. I downloaded Goomanager and attempted to get TWRP using the Install Openrecovery Script option. However, it said that it couldn't find a recovery for my device. I also tried to use the adb method, but nothing happened after I put in the commands. I even tried to flash the latest TWRP .tar file from their website using Odin, but it keeps failing. Is there any way to get TWRP on my phone?
EDIT:Whoops, I skipped over the EZ-Unlock step. Now everything works. Thanks for the help, Sandman!
mikestrong19 said:
I am following the directions in the thread linked above to root and install TWRP. So far, I have the rooted stock ROM running fine, but I can't get TWRP to work. I downloaded Goomanager and attempted to get TWRP using the Install Openrecovery Script option. However, it said that it couldn't find a recovery for my device. I also tried to use the adb method, but nothing happened after I put in the commands. I even tried to flash the latest TWRP .tar file from their website using Odin, but it keeps failing. Is there any way to get TWRP on my phone?
EDIT:Whoops, I skipped over the EZ-Unlock step. Now everything works. Thanks for the help, Sandman!
Click to expand...
Click to collapse
No problem bro. Glad you are all fixed up
Sent from my SCH-I535 using Tapatalk
Sandman-007 said:
No problem bro. Glad you are all fixed up
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Alright, maybe I'm not quite fixed up yet. I have TWRP installed and I can go between TWRP, download mode, and the normal stock rooted ROM fine. However, I cannot get to the SD Card in TWRP in order to install CM. TWRP gives me the following errors upon booting into recovery:
E: Unable to find parition size for '/boot'
E: Unable to find parition size for '/data'
E: Unable to find parition size for '/recovery'
Updating partition details:
E: Unable to mount '/system'
E: Unable to mount '/cache'
E: Unable to mount '/cache'
E: TWFunc: :Copy_Log - - Can't open destination log
E: Unable to mount '/cache'
Upon trying to go to Install, I am unable to select the external SD card, and an additional error appears when I attempt to touch Micro SD Card (E: Unable to mount '/external_sd').
I guess I could try to sideload the CM zip file through adb, but I would rather fix the SD card for future use. I have been researching and working on the SD card for the better part of today, to no avail. I am pretty sure the issue is in the formatting of the SD card (it appears to be RAW rather than the required FAT32 for CM), but I cannot format the SD card into FAT-32 no matter what I try (both Windows and 3rd party formatting tools). They all say that the SD card is either write-protected (I have already checked the read/write switch on the side of the SD card adapter) and/or the format cannot be completed. I have tried both my old SD card that I have kept for a few phones (an 8GB Samsung microSD card) and a brand new Sandisk 8GB microSD card, both of which will not work.
I am able to transfer files to the SD card with no issue (with both ADB and through dragging/dropping in Windows), but I cannot install from SD in recovery.
Does anyone have a solution to allow me to install CM on my phone?
Download root checker from the play store. Make sure you are rooted
Sent from my SCH-I535 using Tapatalk
Sandman-007 said:
Download root checker from the play store. Make sure you are rooted
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Yes, I do have root access. I think the problem lies somewhere in my SD card.
mikestrong19 said:
Yes, I do have root access. I think the problem lies somewhere in my SD card.
Click to expand...
Click to collapse
Do you have another computer to try formatting the sdcard with? And you said that you receive the same errors when trying to reformat the new 8 GB sdcard as with your other sdcard which is formatted to RAW?
SlimSnoopOS said:
Do you have another computer to try formatting the sdcard with? And you said that you receive the same errors when trying to reformat the new 8 GB sdcard as with your other sdcard which is formatted to RAW?
Click to expand...
Click to collapse
I do have access to another computer, but I ran out of time and patience yesterday. I will try it when I get home later today. And yes, both cards are RAW (even the new one) and I can't get either one to format or work in TWRP.
So it appears the the issue with formatting was due to my computer's drivers (even though I installed the latest Samsung USB drivers) and not the SD card. I was able to format the SD card to FAT32 on another computer and put CM and GAPPS onto it. When booted normally into TouchWiz, the phone sees the SD card fine. However, I still get the same "Can't mount external SD card" error as well as the others previously listed when I attempt to install a zip from recovery. I even tried to sideload the ROM from ADB, but it still didn't work.
mikestrong19 said:
So it appears the the issue with formatting was due to my computer's drivers (even though I installed the latest Samsung USB drivers) and not the SD card. I was able to format the SD card to FAT32 on another computer and put CM and GAPPS onto it. When booted normally into TouchWiz, the phone sees the SD card fine. However, I still get the same "Can't mount external SD card" error as well as the others previously listed when I attempt to install a zip from recovery. I even tried to sideload the ROM from ADB, but it still didn't work.
Click to expand...
Click to collapse
Which version of CWM and also TWRP are you using?
And the problems keep rolling in. I was able to mount my SD card and get rid of the TWRP errors by installing a modded TWRP 2.6.0.0 from this thread (http://forum.xda-developers.com/showthread.php?p=44277901). However, when I go to install CM (cm-10.1.3-d2vzw.zip), I get the following error:
assert failed: getprop("ro.product.device") ==
E: Error executing updater binary in zip '/external_sd/cm-10.1.3-d2vzw.zip'
Error flashing zip '/external_sd/cm-10.1.3-d2vzw.zip'
Updating partition details
I did a factory reset before attempting to install this, but I did not format data or do anything else.
mikestrong19 said:
And the problems keep rolling in. I was able to mount my SD card and get rid of the TWRP errors by installing a modded TWRP 2.6.0.0 from this thread (http://forum.xda-developers.com/showthread.php?p=44277901). However, when I go to install CM (cm-10.1.3-d2vzw.zip), I get the following error:
assert failed: getprop("ro.product.device") ==
E: Error executing updater binary in zip '/external_sd/cm-10.1.3-d2vzw.zip'
Error flashing zip '/external_sd/cm-10.1.3-d2vzw.zip'
Updating partition details
I did a factory reset before attempting to install this, but I did not format data or do anything else.
Click to expand...
Click to collapse
Well, that is for the Sprint S3 my friend. We can't interchange recoveries between the different S3 models to flash roms. You may want to ask Kennyglass123 or any of those other guys if they can make a change for the VZW S3 for you to test it out.
SlimSnoopOS said:
Well, that is for the Sprint S3 my friend. We can't interchange recoveries between the different S3 models to flash roms. You may want to ask Kennyglass123 or any of those other guys if they can make a change for the VZW S3 for you to test it out.
Click to expand...
Click to collapse
Sounds good. I think the problem has been isolated to being something with needing a modded TWRP. I tried using an older, non-modded TWRP (2.5.0.0), which didn't work.
mikestrong19 said:
Sounds good. I think the problem has been isolated to being something with needing a modded TWRP. I tried using an older, non-modded TWRP (2.5.0.0), which didn't work.
Click to expand...
Click to collapse
Would you mind trying this soft brick fix? If I'm not mistaken, I believe you're experiencing this same issue--excluding the Sprint TWRP issue you just mentioned. You will need to flash your VZW custom recovery either through GooManager, Rom Manager, or Odin btw.
SlimSnoopOS said:
Would you mind trying this soft brick fix? If I'm not mistaken, I believe you're experiencing this same issue--excluding the Sprint TWRP issue you just mentioned. You will need to flash your VZW custom recovery either through GooManager, Rom Manager, or Odin btw.
Click to expand...
Click to collapse
I can still get between the stock rooted ROM, download mode, and recovery mode fine, so does that mean I am still soft-bricked and should try this?
mikestrong19 said:
I can still get between the stock rooted ROM, download mode, and recovery mode fine, so does that mean I am still soft-bricked and should try this?
Click to expand...
Click to collapse
Yea, because you are still receiving these errors right?
E: Unable to find parition size for '/boot'
E: Unable to find parition size for '/data'
E: Unable to find parition size for '/recovery'
Updating partition details:
E: Unable to mount '/system'
E: Unable to mount '/cache'
E: Unable to mount '/cache'
E: TWFunc: :Copy_Log - - Can't open destination log
E: Unable to mount '/cache'
Click to expand...
Click to collapse
This soft brick fix is an attempt to correct the /system and /data errors.
Edit: Oh great, none of the links work. I'll see about finding alternate links.
Has anyone experienced issues with TWRP being unable to mount the file system?
I can't seem to mount file system while in the recovery. Get the following:
E: Unable to mount 'external_sdcard'
TWRP can't deal with NTFS or exFAT. Is it fat32?
berndblb said:
TWRP can't deal with NTFS or exFAT. Is it fat32?
Click to expand...
Click to collapse
I'm not sure. Whatever the standard is for CROMi-X and Asus .14 bootloader?
abracadabra11 said:
Has anyone experienced issues with TWRP being unable to mount the sdcard?
I can't seem to mount sdcard while in the recovery. Get the following:
E: Unable to mount 'external_sdcard'
Click to expand...
Click to collapse
What I meant was, that your external MicroSD may be formatted in NTFS or exFAT and then TWRP won't see it. It has to be FAT32. If you ever formatted that card on your PC, that may be the problem. If not, the card could be faulty??? IDK
I assume you went to 'Mount' in TWRP and the MicroSD is not checked?
Describe a little more what you are trying to do.
berndblb said:
What I meant was, that your external MicroSD may be formatted in NTFS or exFAT and then TWRP won't see it. It has to be FAT32. If you ever formatted that card on your PC, that may be the problem. If not, the card could be faulty??? IDK
I assume you went to 'Mount' in TWRP and the MicroSD is not checked?
Describe a little more what you are trying to do.
Click to expand...
Click to collapse
Nope - I don't have a MicroSD card. I was just trying to mount the data on the tablet. My initial post wasn't clear - I was try to mount the file system on the tablet and the only error generated was specific to mounting the sdcard (which I don't have).
I couldn't have titled the original post any worse.
abracadabra11 said:
I was try to mount the file system on the tablet and the only error generated was specific to mounting the sdcard (which I don't have).
Click to expand...
Click to collapse
What exactly did you do, what exactly did you expect to happen, and what exactly did happen?
abracadabra11 said:
Nope - I don't have a MicroSD card. I was just trying to mount the data on the tablet. My initial post wasn't clear - I was try to mount the file system on the tablet and the only error generated was specific to mounting the sdcard (which I don't have).
I couldn't have titled the original post any worse.
Click to expand...
Click to collapse
I am confused: You are trying to do what and why???????
berndblb said:
I am confused: You are trying to do what and why???????
Click to expand...
Click to collapse
I am trying to access files on the tablet while booted into recovery. I've used this option with my phone and was hoping to do it with the tablet.
Hi everybody,
so I've got the following problem:
Some of the partitions on my HTC Sensation seem to be FUBAR thanks to my stupid ass trying to wipe /data, /cache and /system with this damn TWRP recovery instead of 4eXT, which is, in my opinion and experience, a gazillion times better. Don't ask me why I tried TWRP in the first place - long story short, the aforementioned partitions can't be mounted (and thus, not formatted either) anymore.
What I can still do is access the device via fastboot (bootloader is HBOOT 1.27, unlocked, S-ON) and flash recoveries like 4eXT and TWRP and, with them, even somehow kernels (namely, SultanXDA's 2.0.2 kernel; at least the AROMA installer says there are no problems) as well as mount an external SD card (even with second and third partitions), but /data, /cache and /system just won't mount for the hell of it.
Do you guys have any idea how I could fix my phone, or is it bricked for good?
I also read somewhere that you can install the entire OS on the SD card, circumventing internal memory altogether, but the guides I found on that are sketchy at best.
I also have a second (working) HTC Sensation here too, if that helps (as in extracting the internal memory and dumping it on the other, but alas, the target device is S-ON...).
Any help would be greatly appreciated!
zylix42 said:
Hi everybody,
so I've got the following problem:
Some of the partitions on my HTC Sensation seem to be FUBAR thanks to my stupid ass trying to wipe /data, /cache and /system with this damn TWRP recovery instead of 4eXT, which is, in my opinion and experience, a gazillion times better. Don't ask me why I tried TWRP in the first place - long story short, the aforementioned partitions can't be mounted (and thus, not formatted either) anymore.
What I can still do is access the device via fastboot (bootloader is HBOOT 1.27, unlocked, S-ON) and flash recoveries like 4eXT and TWRP and, with them, even somehow kernels (namely, SultanXDA's 2.0.2 kernel; at least the AROMA installer says there are no problems) as well as mount an external SD card (even with second and third partitions), but /data, /cache and /system just won't mount for the hell of it.
Do you guys have any idea how I could fix my phone, or is it bricked for good?
I also read somewhere that you can install the entire OS on the SD card, circumventing internal memory altogether, but the guides I found on that are sketchy at best.
I also have a second (working) HTC Sensation here too, if that helps (as in extracting the internal memory and dumping it on the other, but alas, the target device is S-ON...).
Any help would be greatly appreciated!
Click to expand...
Click to collapse
Read this thread
http://forum.xda-developers.com/htc-sensation/help/recovering-data-mount-issues-t2859588
rzr86 said:
Read this thread
http://forum.xda-developers.com/htc-sensation/help/recovering-data-mount-issues-t2859588
Click to expand...
Click to collapse
Did that already. Didn't help, or otherwise I wouldn't come asking again
did you fix it ??