I wanted to start this thread so we can a place where everyone who discovers this issue, comes here and posts on what they did, how they managed to recover from it, and what steps they have taken on preventing this from happening.
I've been lurking around and it seems as if it's the users with the gfree method thats it's only happening too.
I wanna keep track how it happens, as the glacier isn't the only one that suffers from this but it's been happening quite often these past few days. Thanks
Please state how it happen, what rom you flashed and or nandroid backup and if you pulled your battery during a flashing, wiping session.
I can confirm that we're not the only ones that this is happening too. G2 users are also having the same exact problem. There seems to be a really good chance of why this is happening because of different emmc chips and or drivers, i'll be looking through irc logs and put out a summary here for all.
And also, check this out. I know our devices varies from the G2 quite a bit, but then again we're using the same rooting method and exploit so it makes sense to check some stuff from there. http://forum.xda-developers.com/showthread.php?p=13234526
I am sorry if I sound like a nood , but I am a noob:© . I used the gfree mathed to root my phone, didn't run into the problem you are discrubing. Mybe I didn't quite get it.
Sent from my HTC Glacier using XDA Premium App
ummm yea.... happened to me today and after trying basically everything (nandroid restore, flash rom via zip, flash official rom via bootloader etc.) nothing worked
It happened when i was using Virtous Fusion and decided to flash back my Cyanogenmod 7 backup. I has the latest clockworkmod 3.0.2.4, Cleared data / cache and ran the restore... after it was done, i rebooted and noticed that it would not go past the Mytouch splash screen... went back to recovery via the vol down + power combo only to be greeted with...
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Nandroid backups dont flash, zip roms flash (or it seems) but doesnt boot, i get errors when i try to wipe, flashing official rom via bootloader gives me the dreaded FAIL-PU after most steps, so yea... im boned lol
Apparently there is a chance to restore if u got the engineering bootloader but i did not at the time. I did root via gfree since the visionary method refused to gain s-off
I wonder if it has something to do with restoring after clearing data/cache instead of directly restoring... I've never cleared those before a restore and I have never had an issue. let's get some other people in here to test that theory.
kimbernator said:
I wonder if it has something to do with restoring after clearing data/cache instead of directly restoring... I've never cleared those before a restore and I have never had an issue. let's get some other people in here to test that theory.
Click to expand...
Click to collapse
You should be clearing data and cache before restores. There are a lot of things in /data that do not carry over well when changing ROMs. I wonder if it's something to do with ClockworkMod 3.x recoveries.
here you go this is my experience:
http://forum.xda-developers.com/showpost.php?p=13709837&postcount=22
All the users who had this trouble Were rooted with gfree. Any users with the first s-off method?
_ice_ said:
here you go this is my experience:
http://forum.xda-developers.com/showpost.php?p=13709837&postcount=22
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA App
mike21pr said:
It happened when i was using Virtous Fusion and decided to flash back my Cyanogenmod 7 backup. I has the latest clockworkmod 3.0.2.4, Cleared data / cache and ran the restore...
Click to expand...
Click to collapse
You know you should do a factory reset via the recovery image prior to flashing any new ROM. ESP when coming from a 2.2 ROM to a 2.3 ROM.
I wonder if that is what is causing the problem. The Clockwork ROM Manager doesn't wipe everything the "factory reset" in the recovery image itself.
neidlinger said:
You know you should do a factory reset via the recovery image prior to flashing any new ROM. ESP when coming from a 2.2 ROM to a 2.3 ROM.
I wonder if that is what is causing the problem. The Clockwork ROM Manager doesn't wipe everything the "factory reset" in the recovery image itself.
Click to expand...
Click to collapse
You don't mean do the "factory reset" on the HBOOT screen do you?
So.. going from say a 2.2.1 stock to 2.3.3, do... (through clockworkmod recovery screen NOT ROM MANAGER APP)
1. wipe data/factory reset
2. wipe cache partition
3. wipe dalvik (optional?)
If you don't use Rom mamaher to load your Roms , would you run in to the same problem.?
Sent from my HTC Glacier using XDA Premium App
h22aboi said:
You don't mean do the "factory reset" on the HBOOT screen do you?
So.. going from say a 2.2.1 stock to 2.3.3, do... (through clockworkmod recovery screen NOT ROM MANAGER APP)
1. wipe data/factory reset
2. wipe cache partition
3. wipe dalvik (optional?)
Click to expand...
Click to collapse
Wipe data factory reset is broken in cwm 3.0.2.4 it hangs when it comes to /data or /cache especially if you have a cooked rom flashed before from an amateur developer.
I noticed that /data or /cache sometimes do not mount properly thus leaving behind corrupted files.
So my advice is to use the advanced format menu in cwm.
1. Wipe dalvik
2.mount /cache, wipe /cache
3. Wait for it, then mount /system, wipe /system
4. mount /data and wipe /data <--- last
Also because some roms come w autowipe feature sometimes when it tries to wipe an already wiped partitions then sectors get corrupted. So if the rom has auto wipe feature built in. You do not need to wipe /system or /data
Sent from my HTC Glacier using XDA App
jdkoren said:
You should be clearing data and cache before restores. There are a lot of things in /data that do not carry over well when changing ROMs. I wonder if it's something to do with ClockworkMod 3.x recoveries.
Click to expand...
Click to collapse
Restoring clears those partitions by itself. I've always been taught that it's only necessary to clear those partitions when you install a new rom, but restoring does it all by itself. I've restored probably more than 15 times without any clearing and it works fine.
Also, I didn't use gfree, and I might not if people get these errors when they do.
Yeah, this is my third mytouch, and this is the only one I used gfree on. I remember with my second one I didn't use the gfree method and I flashed and did everything without any of these risks. Im stilling leaning towards the gfree method being the culprit for the recovery errors.
kimbernator said:
Restoring clears those partitions by itself. I've always been taught that it's only necessary to clear those partitions when you install a new rom, but restoring does it all by itself. I've restored probably more than 15 times without any clearing and it works fine.
Also, I didn't use gfree, and I might not if people get these errors when they do.
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA App
xdviper said:
Yeah, this is my third mytouch, and this is the only one I used gfree on. I remember with my second one I didn't use the gfree method and I flashed and did everything without any of these risks. Im stilling leaning towards the gfree method being the culprit for the recovery errors.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
yes sir, that could be another factor. gfree is mainly for CID unlock and "true root" but thing is true root isn't required... every other rom flashes -.- gfree also alters your dev block partition which can cause issues.
This thing has me a little worried.
I used the gfree method from the CM Wiki for the Glacier. I have s-off and hboot .85, but I am a bit more hestitant now to flash different roms seeing as how many people are having problems. However, I don't like Rom Manager and never use it. I always go through CWR to flash so is that better? And I am on 3.0.0.6.
FYI, according to trueblue_drew he says to do this as far as wiping your stuff on flashing one of his roms...
This is how you should wipe:
Main Recovery Menu:
1. Wipe data / factory reset
2. wipe cache partition
Advanced Recovery Menu:
3. Wipe Dalvik Cache
Mounts and Storage Recovery Menu:
4. Format System
Sent from my HTC Glacier using XDA
I got the fail PU error a week ago. I was on an miui rom and was restoring a backup I had of cm7. When I rebooted after the restore the phone would not load past the splash screen. I booted back into recovery and noticed the E: Can't mount/cache errors. I tried to flash a new rom but when I would reboot it would not go past the splash screen still. That's when I looked up the problem. I then tried to restore with the PD15IMG, but got the fail PU errors. I then read that you need the part7backup on the sd card if you are going to use the PD15IMG. So I did and stilll got the fail PU errors, but this time it was stuck loading the radio. I pulled the battery. Would not even turn on after that.
I too had rooted with the gfree method and had the engineering bootloader.
I called T-mobile to replace the phone since it wouldn't even turn on anymore. Took 2 hours to get them to send a replacement with free shipping. They accidentally sent me 2. Two separate boxes, same shipping number. At least now I have a backup. I already rooted one. I did not use the gfree method this time.
Since it seems to be a gfree problem, should I go to stock and re-root the phone using another method??
tilt4life2 said:
Since it seems to be a gfree problem, should I go to stock and re-root the phone using another method??
Click to expand...
Click to collapse
Well, that's what I'm probably going to end up doing as well. This is my third replacement and the first method to root didn't stick, so I ended up rooting with gfree. I am going to unroot and try rooting with the first method which is here http://theunlockr.com/2010/12/10/how-to-gain-permanent-root-and-s-off-on-the-t-mobile-mytouch-4g-htc-glacier/ but the thing is, if it doesn't stick, we're back at gfree.
Anyone know any G2 users that have/had this problem? We're using the same rooting method so there should be a couple people who faced this.
Alright well I've been reading logs from G2_Root channel from April 26th and so on, and it looks like the G2 has two different types of the emmc chip. Gfree powers off this chip and then initializes the chip again in order to get around the write protection. I remember before we had root access on the G2 (before I traded for a mytouch) I would lurk around the irc channel and read progress. I remember having to get the chip to power on in order to get around the write protection.
Now it looks like while the phone is being used, or booting up and or trying tto read or write from emmc the chip suddenly dies. This is what causes us to get force closes, freezes and not being able to get past the splash screen and also explains the recovery not being able to mount partitions.
We're going to need people to join in the G2 channel preferably ones who still have their defective phones to get some data off it.
Again, this is a very vague summary of what I've been able to read off the irc logs.
Why the G2? Because we're using the same gfree method to root our phones and with our phones dying it makes sense.
I think, they have already ruled out recovery and the Eng hboot to be culprit but this is just too early in the game to determine.
Here's a thread from the G2 side, if anyone still has this problem with their cache not being to mount please check out post #13.
I'll look.around more and see what I find from the G2 side.
http://forum.xda-developers.com/showthread.php?t=1039504
Sent from my HTC Glacier using XDA App
Related
Last night, I decided to try out the Trinity kernel. I downloaded and flashed, and everything went without error. After that, I pushed a custom boot animation over ADB. The first one didn't work, and after the splash screen disappeared it was simply a black screen, but then I pushed one I downloaded from XDA and it was fine.
Now, though, I want to make a nandroid, but CWM is running into some issues. I started the ROM manager app, entered a name for the nandroid as usual, and hit OK, but when it rebooted into nandroid, it gave me an error saying "Error mounting /system" and rebooted back into CM7. That's odd, I thought, I never had any problems like that before. So I rebooted into CWM myself by holding down power+vol down and tried making a nandroid there. No luck. Then I went to mounts and storage and tried to manually mount /system. CWM gave me the error again.
I'm not really sure what's causing this. I thought it might be because now I'm using an ext4 filesystem because of Trinity (right? haha I'm new to kernels and such) and CWM might not support reading it, but if that's the case, I think I would not be the first to have this issue. Yet I searched, on that thread, on Google, on XDA general search, and didn't see anything. I also doubt it's the boot animation.
My last nandroid was yesterday. The only changes to the system I remember right now is that I flashed CM7 nightly 101, then flashed Trinity, rebooted, and flashed the boot animation mentioned. I installed apps since then but none of them had root so I doubt that's it. I would reflash CM7 to overwrite Trinity, but I read on the Trinity thread that if I did that without restoring an old CM7 kernel nandroid first, I'd be stuck in a bootloop because of ext4...?
So, what should I do? I don't want to make anything worse than it already is by tinkering with this myself, I no longer have a current nandroid, that's why I'm asking XDA. Does anyone have an idea why this might be happening? I'm sorry if a thread like this already exists or if this is in the wrong forum (if so mods please move it), this is my first time posting and my search skills could suck (although I looked in all the places I could think of)
Thanks for your help! My G2x is running CM7 nightly 101. Both the nvflashed CWM in recovery and the CWM started by the rom manager app are version 3.0.2.7.
I got the same problem as you bro right after flashing trinity
Sent from my LG-P999 using XDA App
ritthyhang said:
I got the same problem as you bro right after flashing trinity
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Good, so I'm not the only one! I thought that was too odd to be true.
Here's what I've done. I reflashed cm7 nightly 101 to get my CM kernel back and rebooted. Sure enough, bootloop. Or it never got past the splash screen to the CM7 android skateboard boot animation. I went back in recovery, though, and was able to mount /system. Odd. So I flashed trinity again and tried mounting /system again and no go. So this definitely has something to do with Trinity... I restored my nandroid, reflashed 101,and that's where I am now. Tomorrow, I will make an up-to-date nandroid and do some tinkering to try to figure out what's going on. Maybe it has something to do with the boot animation, maybe not, exactly what's going on is what I am going to try to figure out if no dev shows up here.
Could you give me a few details about your case? Were you coming from cm7 too? Did you do any boot animation tinkering like me?
Sent from my LG-P999 using XDA App
Okay so I was eaglesblood 1.6 and flashed trinity the other day. Before trinity I was on miui and made plenty of nandroid backup. So today and 1.7 got released so before update I try to backup then behold Our Problem. So after I confirm that I can flash 1.7 over 1.6 I decided to take that risk and flashed anyways. On 1.7 the Superuser was updated I notice, so I decided to make a backup and it Work. So I think the problem was had to do with the outdated Superuser. I think I might be wrong that's just my experience.
Sent from my LG-P999 using XDA App
ritthyhang said:
Okay so I was eaglesblood 1.6 and flashed trinity the other day. Before trinity I was on miui and made plenty of nandroid backup. So today and 1.7 got released so before update I try to backup then behold Our Problem. So after I confirm that I can flash 1.7 over 1.6 I decided to take that risk and flashed anyways. On 1.7 the Superuser was updated I notice, so I decided to make a backup and it Work. So I think the problem was had to do with the outdated Superuser. I think I might be wrong that's just my experience.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Hmm. So to clarify: You were running MIUI, then you flashed eb followed by trinity. Then, eb 1.7 was released and you went to nandroid, but you couldn't mount /system, so you took the risk and upgraded anyways. The new be came with a new version of superuser, and you were able to make nandroids once again. Is this correct?
One very important question if it is. Did you flash trinity again after flashing the eb 1.7 update?
Also, could I ask what version of superuser came in this update? I am using version 2.3.6.3, which is the latest according to Superuser check for updates, but ROM Manager lists a 3.0 beta version and I'm wondering if you're using that. To check, open Superuser, go to the settings tab, and scroll all the way down. It's the second to last option for me. It's unlikely that superuser is making the difference, since it works as a part of Android and our problem is in recovery, before Android loads, but I can see how it might be possible. If you're using the 3.0 beta, I will flash to that and see if it fixes.
I will look into this some more tomorrow, specifically right now I want to know what filesystem eb's kernel recommends.
Sent from my LG-P999 using XDA App
G2X here same problem.
I think they key here is MIUI. I tried to load MIUI image and it didnt go well. I formatted and CWR to restore and its been giving me issues same cant mount system errors.
Right now I downloaded CM7 and installed it from scratch and I can use the phone but it wont backup my ROMs anymore.
Have you guys found anything new ?
lithivm said:
I think they key here is MIUI. I tried to load MIUI image and it didnt go well. I formatted and CWR to restore and its been giving me issues same cant mount system errors.
Right now I downloaded CM7 and installed it from scratch and I can use the phone but it wont backup my ROMs anymore.
Have you guys found anything new ?
Click to expand...
Click to collapse
Update cwm to latest recovery 5.0.2.0 i believe.
fcisco13 said:
Update cwm to latest recovery 5.0.2.0 i believe.
Click to expand...
Click to collapse
+1 cwmr 5.0.2 is the first to officially support ext4 partitions
Sent from my LG-P999 using xda premium
lithivm said:
I think they key here is MIUI. I tried to load MIUI image and it didnt go well. I formatted and CWR to restore and its been giving me issues same cant mount system errors.
Right now I downloaded CM7 and installed it from scratch and I can use the phone but it wont backup my ROMs anymore.
Have you guys found anything new ?
Click to expand...
Click to collapse
I just stopped using Trinity and went back to the stock CM kernel. I don't think it's just miui, I never used that. But...
fcisco13 said:
Update cwm to latest recovery 5.0.2.0 i believe.
Click to expand...
Click to collapse
squish099 said:
+1 cwmr 5.0.2 is the first to officially support ext4 partitions
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
YESS! Looks good. I did hear about that. Looks like it's time to give Trinity another try
Error mount/system!
I can't restore my stock rom,i've tried to fully wipe but got:
-- Wiping data...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Data wipe complete.
and cant restore
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Error mounting /system!
Skipping format
Can't mount /system!
and cm7 doesnt boot,now im just stuck in ClockworkMod Recovery v4.0.0.5
is there any ways to flash stock rom in clockworkmod??
asn_86 said:
I can't restore my stock rom,i've tried to fully wipe but got:
-- Wiping data...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Data wipe complete.
and cant restore
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Error mounting /system!
Skipping format
Can't mount /system!
and cm7 doesnt boot,now im just stuck in ClockworkMod Recovery v4.0.0.5
is there any ways to flash stock rom in clockworkmod??
Click to expand...
Click to collapse
Update your recovery, both, fake and nvflash.
i was also having the can't load system issue. upgrading to latest clockwork mod via rom manager to v5.0.2.0 resolved the issue and i was able to take a backup of my current system.
jblah said:
i was also having the can't load system issue. upgrading to latest clockwork mod via rom manager to v5.0.2.0 resolved the issue and i was able to take a backup of my current system.
Click to expand...
Click to collapse
Where do I find the latest clockwork mod and how do I install it? I currently have a soft bricked phone, and I can't seem to get it unbricked. I tried using the pit files with the stock rom, the dbdata stuff and everything else. What happened was the the system was in ICS, but something happened and I couldn't load into CWM 4 and the system wouldn't boot. So to fix, I used odin to install the stock rom (v2.3.3), but the stock rom came with CWM 3.0, so now I'm at 3.0 and can't mount the file system and it's not booting. I'm assuming that if I upgraded the CWM back to a newer version, I'll be able to restore the system and gain access to the file system again.
reboot problem
i jus flashed ext4 converter for kernel update every think went fine but i couldnt mount system coz it was showing error i neglected dat nd flashed every thing was done nd when i rebooted it gt stuck in d samsung galaxy y logo...plzzz help meee wat to do..plzzz help
Abizer98 said:
i jus flashed ext4 converter for kernel update every think went fine but i couldnt mount system coz it was showing error i neglected dat nd flashed every thing was done nd when i rebooted it gt stuck in d samsung galaxy y logo...plzzz help meee wat to do..plzzz help
Click to expand...
Click to collapse
I'd ask in the samung galaxy forums bud.
"my mind draws lots of blanks actually"
Solution
asn_86 said:
I can't restore my stock rom,i've tried to fully wipe but got:
-- Wiping data...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Data wipe complete.
and cant restore
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Error mounting /system!
Skipping format
Can't mount /system!
and cm7 doesnt boot,now im just stuck in ClockworkMod Recovery v4.0.0.5
is there any ways to flash stock rom in clockworkmod??
Click to expand...
Click to collapse
actually yes. the /system folder is corrupt and it need to be formatted. so all you need to do is format / system then it will work as it should
hope that helps
Ok
I know i'm sorry if this has been posted quite a lot but i can't find a proper answer. I installed the leaked sense 3.0 rom and everything went fine. But suddenly the phone switched off and everytime i boot i get stuck on the white htc screen. i can get into recovery but when i do i get
E: can't find cache.... (will have to check error later properly)
Anyway i've tried factory reset, installing a new rom, installing recovery again and also running the RUU software. The RUU software was my last option and i'm getting stuck at rebooting to bootloader. Is this a faulty eMMC chip or do i still have other options. My device is S-OFF and rooted, so is there anyway to change it back for warranty purposes?
Any help will be appreciated a lot!!!!!
dan-fish said:
i can get into recovery but when i do i get
E: can't find cache.... (will have to check error later properly)
Click to expand...
Click to collapse
I'm afraid that it does sound very like the symptoms of the fried eMMC chip problem. Did you at any point pull the battery?
If you attempt to go into RECOVERY and try to format the CACHE partition what errors do you get?
Do you have any Full Nandroid backups on your SD card that you can attempt to restore?
i have taken the battery out many times to get into recovery when i have boot loops and what not. Also have done it a lot now to get into recovery
i didn't have a backup so i copied one over from my brothers desire s which i had hoped would still work. I'm not sure if it was because it was from my brother's phone or it was because everything refuses to work, but the restore didn't work.
also clockworkmod is just really slow.
when i wipe the cache it says
-- Wiping cache
Formatting /cache...
Cache wipe complete
Then shows the original error again which is
E:Can't mount /cache/recovery/log
E:can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
So the cache wiping is a success but does that help in any way. Is the eMMC chip still most likely fried?
I tried installing cm7 and it gave me the error
E:Error in /sdcard/update-cm-7.1.0-RC1-DesireS-Nexx-signed.zip
(Status 1)
Installation aborted
I know for a fact the rom is fine because my brother has the rom on his desire s.
dan-fish said:
i have taken the battery out many times to get into recovery when i have boot loops and what not. Also have done it a lot now to get into recovery
i didn't have a backup so i copied one over from my brothers desire s which i had hoped would still work. I'm not sure if it was because it was from my brother's phone or it was because everything refuses to work, but the restore didn't work.
also clockworkmod is just really slow.
when i wipe the cache it says
-- Wiping cache
Formatting /cache...
Cache wipe complete
Then shows the original error again which is
E:Can't mount /cache/recovery/log
E:can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
So the cache wiping is a success but does that help in any way. Is the eMMC chip still most likely fried?
I tried installing cm7 and it gave me the error
E:Error in /sdcard/update-cm-7.1.0-RC1-DesireS-Nexx-signed.zip
(Status 1)
Installation aborted
I know for a fact the rom is fine because my brother has the rom on his desire s.
Click to expand...
Click to collapse
I'm afraid that it does seem to be yet another fried eMMC chip...see this thread that I only answered yesterday that exhibits exactly the same problem and has a couple of linked threads in it. Although I'm by no means an expert, so dig around through the various related threads on this subject to confirm this for yourself. I have seen a thread a while back within this forum, although can't find it now that shows commands and then the results returned from a bricked (fried eMMC chip) device and a non bricked device that will enable you to confirm 100%.
Although, it does look like service centre will be your next stop, if you're lucky they may fail to notice the S-OFF state of the device.
so there is absolutely no way to go back to s-on? Is there at least a way to make sure they don't realise it's S-OFF?
dan-fish said:
so there is absolutely no way to go back to s-on? Is there at least a way to make sure they don't realise it's S-OFF?
Click to expand...
Click to collapse
I would also like to know this information incase it ever happened to me
daveys4 said:
I would also like to know this information incase it ever happened to me
Click to expand...
Click to collapse
Right now i would prefer it if my phone were actually bricked!
Can i just send them the phone without the battery or sd card?
Also how does fastboot work?
I want to try something like this http://forum.xda-developers.com/showthread.php?t=1231249
But when i type in fastboot oem lock in cmd nothing happens
dan-fish said:
so there is absolutely no way to go back to s-on? Is there at least a way to make sure they don't realise it's S-OFF?
Click to expand...
Click to collapse
I'll be honest I don't know.
Does adb recognise your device still? So question is does adb or fast boot function?
Now the post that I mentioned earlier may be of some use at this point.
I'm about to PM you something.
Swyped from HTC Desire S using XDA Premium
dan-fish said:
Right now i would prefer it if my phone were actually bricked!
Can i just send them the phone without the battery or sd card?
Also how does fastboot work?
I want to try something like this http://forum.xda-developers.com/showthread.php?t=1231249
But when i type in fastboot oem lock in cmd nothing happens
Click to expand...
Click to collapse
You need the adb and fast boot exe on your PC which you can get online, afraid that I'm away from a PC now so will have to add more tomorrow
I've send you a pm (a last resort)
Swyped from HTC Desire S using XDA Premium
i most likely will not have time today but tomorrow i'll try and get the hang of adb and fastboot. Explore my options with it. If nothing happens i'll just have to call htc.
I was thinking if i can't do anything else, i should just drain the battery by swapping the battery with my brother's desire s, drain the battery and then swap them back. Maybe that'll help?
dan-fish said:
i most likely will not have time today but tomorrow i'll try and get the hang of adb and fastboot. Explore my options with it. If nothing happens i'll just have to call htc.
I was thinking if i can't do anything else, i should just drain the battery by swapping the battery with my brother's desire s, drain the battery and then swap them back. Maybe that'll help?
Click to expand...
Click to collapse
You'll see in my Signature the links to get both ADB and FASTBOOT, you'll also need HTC drivers installed.
This is the usefull THREAD that I was talking about.....in determining whether you are indeed suffering from fried eMMC chip, even though at this stage we're reasonably confident.
ben_pyett said:
I'm afraid that it does seem to be yet another fried eMMC chip...see this thread that I only answered yesterday that exhibits exactly the same problem and has a couple of linked threads in it. Although I'm by no means an expert, so dig around through the various related threads on this subject to confirm this for yourself. I have seen a thread a while back within this forum, although can't find it now that shows commands and then the results returned from a bricked (fried eMMC chip) device and a non bricked device that will enable you to confirm 100%.
Although, it does look like service centre will be your next stop, if you're lucky they may fail to notice the S-OFF state of the device.
Click to expand...
Click to collapse
That is not a fried chip! If he can get into recovery and wipe cache it definately isn't a fried chip, i had this 2 days ago. I sorted it somehow..... been drinking tonight so don't expect an answer until late tomorrow
Malooga said:
That is not a fried chip! If he can get into recovery and wipe cache it definately isn't a fried chip, i had this 2 days ago. I sorted it somehow..... been drinking tonight so don't expect an answer until late tomorrow
Click to expand...
Click to collapse
@Malooga
It would obviously be quality if it's not and the device is recoverable from this position. Any clues how you sorted this out, using what approach?
@dan-fish
Do you have EXT4 recovery installed?
If you do great. If not then 1) download this FILE 2) copy it onto your SD card 3) enter recovery 4) flash the EXT4 ZIP file 5) then Reboot Recovery.
Using EXT4 recovery, look at what format the existing CACHE partition and the other partitions are in? this can be done using the EXT3 - 4EXT - 4EXT option of the EXt4 recovery main screen.
I'd also try to download a custom ROM WIPE script and then run this from recovery (reporting back any errors).
Then try to flash a custom ROM also again also from recovery having downloaded it to your SD card like LBC using the flash ZIP from SD card option in recovery.
Will try later today. Please do try and help malooga
Sent from my HTC Desire S using XDA Premium App
dan-fish said:
Will try later today. Please do try and help malooga
Sent from my HTC Desire S using XDA Premium App
Click to expand...
Click to collapse
Although Malooga might be suffering today from the morning after (we've all been there)
I'll be online most of the day, as I'm currently off work sick...as I've somehow knackered my back - so XDA is keeping me sane
installing 4ext recovery
assert failed: write_raw_image (" /tmp/recovery.img" , "recovery"
E:Error in /sdcard/4EXTRecovery_v2.1.3RC2.zip
(Status 7)
Installation aborted.
Ran full wipe script:
E:Error in /sdcard/FULL_WIPE_1.5_EXT4-for-saga_.zip
(Status 1)
Installation aborted
Seriously running out of options.
I had this happen I just wiped data factory reset wipe cache wipe dalvik then go into mounts and format data format cache format system then flashed my backup the phone then booted up if u don't have a backup download a rom zip and flash that if you have tried the above then I'm all out of ideas good look
Sent from my HTC Desire S using xda premium
As you don't have any Backups.....we should attempt to move forward.
As we know that you can format/wipe partitions (eg CACHE appeared to work) you should try to manually format/wipe DATA, SYSTEM and CACHE.
Download a custom ROM to your SD card ie LBC like LBC v0.5.3
Then try to flash this Custom ROM from RECOVERY using the flash ZIP from SD card option.
Report back any errors and progress.
ok will try now and update in 10-15 mins.
also i haven't explored my options with fastboot mainly because i don't really understand it yet but if there are any options available through there (excluding the last resort which right now is looking like our only option) i will be happy to try
dan-fish said:
ok will try now and update in 10-15 mins.
also i haven't explored my options with fastboot mainly because i don't really understand it yet but if there are any options available through there (excluding the last resort which right now is looking like our only option) i will be happy to try
Click to expand...
Click to collapse
I'm by no means an expert either and fastboot is something that I've yet to master..so before you try that EVIL one.....lets try some other stuff and look for advice from others.......
I'm online tonight for next couple of hours, we'll until the England Football game kick offs anyway!
Following situation: I have bought a Nexus S from someone. The previous owner installed Superuser at some point and later on updated to ICS 4.0.3 (and unrooted the phone as well before the update, apparently). For warranty reasons, I want to remove the Superuser application completely, but naturally I can only do that by rooting the phone again (otherwise I will not be able to delete /system/app/Superuser.apk).
I searched around here and other sites around the web and found a few guides, but haven't found anything specifically for the i9023 with ICS 4.0.3, especially for unrooting.
Could someone may be point me in the right direction? Or is there simply no way of doing that currently on an i9023 with ICS 4.0.3?
The best thing to do would be to root, flash a stock image (incl bootloader and recovery). Then relock the bootloader, and you're all done
Also, recently some sort of flash counter resetter has come to light for ICS devices, look it up and check it out before you unroot, it might be worth the probable risk, if you're willing to go the distance to ensure a warranty. I have no clue on how or if it works though, be careful.
One question though, do you actually have any warranty seeing as you bought the device used? If not, why not just reroot it and enjoy that?
Erythnul said:
The best thing to do would be to root, flash a stock image (incl bootloader and recovery). Then relock the bootloader, and you're all done
Also, recently some sort of flash counter resetter has come to light for ICS devices, look it up and check it out before you unroot, it might be worth the probable risk, if you're willing to go the distance to ensure a warranty. I have no clue on how or if it works though, be careful.
One question though, do you actually have any warranty seeing as you bought the device used? If not, why not just reroot it and enjoy that?
Click to expand...
Click to collapse
Nexus S doesn't have a flash counter
Sent from my ice cream powered Nexus S
Erythnul said:
The best thing to do would be to root, flash a stock image (incl bootloader and recovery). Then relock the bootloader, and you're all done
Click to expand...
Click to collapse
I already went ahead and tried that, but I ran into a problem unfortuantely: http://forum.xda-developers.com/showthread.php?p=22599816#post22599816
Other users on a german Android forum reported the same problem, when using this method (the Nandroid backup image and restoring it via CWM). They then tried a different method using Odin.
(Funnily enough, when I reverted to my original ICS 4.0.3 backup image via CWM, my USB Transfer Speed problem got fixed. I only had 1 MiB/sec before, and now after this whole ordeal I have ~20 MiB/sec (or more).)
Erythnul said:
One question though, do you actually have any warranty seeing as you bought the device used? If not, why not just reroot it and enjoy that?
Click to expand...
Click to collapse
I do still have warranty on it. The device was bought on 14th of December 2011 and I have the receipt. According to the seller, he got a Galaxy Nexus on Christmas 2 weeks later, so he simply sold his brand new Nexus S.
I may want to send the phone in, because the phone speaker is a bit bad. It's not completely broken, I can still understand everything, but the quality is rather bad, some frequencies get really distorted etc. I don't know if the Samsung support partner where I'll go to will grant me the warranty here, but I want to try nonetheless. Paid too much money for it to have a bad speaker .
In my opinion, you should never use other people's CWM backups on your own phone. It can mess things up BAD. Especially when they don't say what model they have.
Grab a full ROM from here: http://forum.xda-developers.com/showthread.php?t=1445635 and you'll be good to go. Don't forget to wipe /system, /data, /cache, /boot, dalvik cache and do a factory reset before flashing, assuming you're using CWM.
Good to hear about the warranty, good luck with that!
Erythnul said:
In my opinion, you should never use other people's CWM backups on your own phone. It can mess things up BAD. Especially when they don't say what model they have.
Click to expand...
Click to collapse
Yeah, well, I am thinking the same now . I simply trusted the stickied FAQ . Maybe this should get removed.
Erythnul said:
Don't forget to wipe /system, /data, /cache, /boot, dalvik cache
Click to expand...
Click to collapse
Phew, but for that, I'd need to root it again, right? I am still not sure if any of the rooting guides I found so far also apply to my case, since I have ICS 4.0.3 on it. (As I said superuser is already installed, but the device is not rooted and it seems to be a leftover from before the ICS 4.0.3 update.)
Well, I wouldn't know Try booting into recovery, if it's CWM recovery it's really very easy, and that's all you'll need anyway. doing the full wipe and reflash guarantees that there'll be no traces of the rooting process remaining at all.
If you don't have CWM, but the phone boots up with an unlocked symbol at the Google logo (first indicator of an unlocked bootloader), you can easily flash CWM again and then flash to all-stock. Then relock. Most rooting guides still hold, just make sure you flash the latest CWM (5.0.2.0 (non-touch) or 5.8.0.x (touch)), especially as for what you want to do you don't need SU, just CWM.
Step-by-step quick guide written by me
Install Android SDK if necessary (for adb and fastboot) (plenty of guides for that around)
download recovery file from CWM and rename to recovery.img
Connect phone to computer and reboot into bootloader
fastboot oem unlock
fastboot flash recovery recovery.img
use CWM to wipe everything and reflash
fastboot oem lock
???
Profit!
Alternately, use a one-click root method to flash CWM and then work from there
Good luck
EDIT: The FAQ you mentioned is probably old news by now, but I wouldn't know how to get that updated I'll see if I can get something done about that. I feel linking to a backup, especially with a dedicated full ROM thread (also stickied btw ) around, isn't a good idea at all
Thx for that.
I did look into CWM before you posted it and noticed these wiping options. However, I am unsure what exactly I should use. There is
- wipe data/factory reset
- wipe cache partition
in the main menu of CWM and
- Wipe Dalvik Cache
under advanced. But there is no specific mention of /system and /boot .
Also is this
download recovery file from CWM and rename to recovery.img
Click to expand...
Click to collapse
actually necessary? I searched around a bit and I thought that I simply have to grab one of the full ROMs (e.g. Android 2.3.6/GRK39F/XXKF1 Radio/KA3 Bootloader) and then use
- install zip from sdcard
in CWM.
Ah, I wasn't sure whether you had CWM on there, that makes all this way easier
The format options are under mounts and storage. Be careful not to wipe the SD, and make backups of stuff you want to keep (like SMS messages or apps etc). What I always do is wipe everything (except the sd-card!) under mounts and storage and then do a factory reset, that should also take care of the dalvik cache if I remember correctly. So just skip everything I said before wipe and reflash
Sounds like you have a good handle on the situation now, good luck on the warranty thing!
Erythnul said:
Ah, I wasn't sure whether you had CWM on there, that makes all this way easier
Click to expand...
Click to collapse
Yes, although I have to flash it every time I want to use it (I guess because the stock Android ICS ROM is removing it on every boot?).
Erythnul said:
The format options are under mounts and storage. Be careful not to wipe the SD, and make backups of stuff you want to keep (like SMS messages or apps etc). What I always do is wipe everything under mounts and storage and then do a factory reset, that should also take care of the dalvik cache if I remember correctly. So just skip everything I said before wipe and reflash
Click to expand...
Click to collapse
Aaah ok, so under
- mounts and storage
I do
- format /system
- format /cache
- format /data
- format /boot
and maybe
- format /sdcard
as well, if I don't need anything on it anymore, and then
- wipe data/factory reset
in the main menu of CWM, correct? And after that
- install zip from sdcard
with the aforementioned ROM.
Exactly, but don't wipe the sdcard, as the ROM you're going to flash is on there
and after that, don't forget to relock your bootloader, if it's still unlocked they'll know it used to be rooted
Erythnul said:
Exactly, but don't wipe the sdcard, as the ROM you're going to flash is on there
Click to expand...
Click to collapse
lol, damn, yeah, that would have been stupid
I posted this in Q&A, but no replies led me to post here as well.
Hi. I've been using this Xoom for a couple weeks now, and just started having this problem yesterday.
Before I noticed the promblem I was on EOS 3 Wingman. I had TWRP 2.2.2.0 as recovery.
I wanted to give CM10 nightlies a shot. Downloaded the ROM and GAPPS through Goo. I tried to flash the CM10 ROM and GApps zip through the Goo interface. Xoom rebooted and instead of installing, I just got a contantly repeating error saying the install failed.
Eventually I rebooted the xoom and went into recovery. I tried to wipe data and it said it couldn't be mounted. Same error for wiping system, cache, etc...
Rebooted xoom and the EOS 3 rom was still working fine, I downloaded [Recovery] ClockworkMod 3.2.0.0 (R4c) Modded for Internal media [UPDATED 10/6]" and flash via adb. rebooted to recovery and tried wipe. same issue. nothing could be wiped. everything said "failure mounting <applicable partition>".
I tried flahing rogue recovery and got the same thing. I said screw it and rebooted back into EOS and it's been working fine. EOS was updated last night to 143, so i downloaded and tried to install through goo. I got the repeating errors again. Rebooted into recovery and still got the errors where it seems like none of the partitions are writeable.
I WAS able to install the EOS update directly through recovery.
Has anyone ever seen this behavior before and know how to fix it? I can't even export logs in the 2 CWM recoveries because they fail when trying to write the log file.
If I try to install an update through goo, it reboots to recover and just keeps scrolling "An Update Error has occured".
I can reboot to recovery and install the zip from there directly with no issue.
Here is the log for the failed data wipe...
I:mke2fs command: mke2fs -t ext4 -m 0 /dev/block/mmcblk0p10
mke2fs 1.41.12 (17-May-2010)
/dev/block/mmcblk0p10 is apparently in use by the system; will not make a filesystem here!
E:Unable to format data.
* Verifying filesystems...
I:=> Let's update filesystem types via verifyFst aka blkid, command: 'blkid'.
* Verifying partition sizes...
Ievice has /data/media
I:Total used space on /data is: 5122715648
I:Total in /data/media is: 3962468352
I:Actual data used: 1160247296
du: /data/media/.android_secure: No such file or directory|
once in recovery, if I try to format data, it says "Unable to format data". Log
Well I can't help, I'm in the same boat...hoping to get some insight from any responses you might get.
grey.ghost said:
Well I can't help, I'm in the same boat...hoping to get some insight from any responses you might get.
Click to expand...
Click to collapse
It's extremely unusual to get no responses to an issue like these here at XDA. leads me to believe it might be a very uncommon problem. The folks here are usually on the ball about any issue that has even arisen before.
That being said, I am going to try to flash the stock RUU back on from this link...
http://developer.motorola.com/produ...utm_source=supportforums&utm_term=unlockboard
After I finish, I re-root/unlock.
I'll let you know how it goes.
I'll let you know if I come up with something as well. So far I've managed to erase the sd card and maintain a constant boot loop.
Flashing all of the stock img, relocking, and unlocking again didn't do ****.
Found an original MZ600 SBF, which is what I need for verizon 3g xoom, I'm installing this via RSD Lite to see if it blows away whatever is causing the issue.
I was able to wipe the entire system and use adb to repeat the unlock and root steps. So far so good. I'm using the CWM 3.2.0.0 recovery image right now though. I have at least been able to get into a clean copy of a ROM and no bootloops yet. Can't restore data off old Nandroids, so I'm about to update to the newer CWM based recovery image and see if that will help.
I think I'm OK now.
I installed the SBF. Let all of the OTA updates come in including the ICS update where my 3g stops.
flashed the ROGUE recovery from fastboot.
I was able to format all partitions and install and boot CM9 nightly.
Me too, i was sweating hard for a bit, but was able to go through the entire process from stock, unlock, root, rogue recovery and then flashed CNA. Got that working without boot loops or fc and then advance restored data from a previous nandroid through rogue to get it back. A couple of apps had to be redownloaded from the market, but it looks as if I'm back in business. I want to try TWRP, but every time I do something screws up, so I think I'll stop trying.
Thanks for the help.
grey.ghost said:
Me too, i was sweating hard for a bit, but was able to go through the entire process from stock, unlock, root, rogue recovery and then flashed CNA. Got that working without boot loops or fc and then advance restored data from a previous nandroid through rogue to get it back. A couple of apps had to be redownloaded from the market, but it looks as if I'm back in business. I want to try TWRP, but every time I do something screws up, so I think I'll stop trying.
Thanks for the help.
Click to expand...
Click to collapse
Are you installing Twrp from goo manager. Cause I have not had any issues with the goo manager download. But did have issues with the zip file here on xda. I dont kknow if it is worth a try but that is how I did it.
Sent from my Xoom using xda app-developers app
Well sense this is a twrp related issue I would think u would have asked in my thread where I released the port for twrp to Xoom,
Having said that, at one point n time there was a note n the open about open script recovery. But its is also buried in the thread too. So I will answer your question and also presume a few things... and please correct me if I am wrong anywhere.
Once u set the download path in goo app to /data/media/goomanager/ and downloaded a ROM, clicked flash ROM, and entered recovery once u saw all the E/ update error u manually rebooted the Xoom and did not let the script finish installing the ROM? If I am correct that so far. That's what cause your additional problems. You basically rebooted recover while mid install of a ROM.
Now as stated it the twrp thread for Xoom, these errors are false errors and should be ignored. To add it the reassurance that they are intact false errors, from goo app select to flash a ROM again and simple allow the script to finish and then the tablet will reboot on its own when it is finished with the script. And you will be greeted with your new ROM you just successfully flashed.
Again let me know if I am wrong on assuming you forced a reboot mid install ( aka while u saw all the errors)
Sent from my Nexus 7 using Tapatalk 2
runandhide05 said:
Well sense this is a twrp related issue I would think u would have asked in my thread where I released the port for twrp to Xoom,
Having said that, at one point n time there was a note n the open about open script recovery. But its is also buried in the thread too. So I will answer your question and also presume a few things... and please correct me if I am wrong anywhere.
Once u set the download path in goo app to /data/media/goomanager/ and downloaded a ROM, clicked flash ROM, and entered recovery once u saw all the E/ update error u manually rebooted the Xoom and did not let the script finish installing the ROM? If I am correct that so far. That's what cause your additional problems. You basically rebooted recover while mid install of a ROM.
Now as stated it the twrp thread for Xoom, these errors are false errors and should be ignored. To add it the reassurance that they are intact false errors, from goo app select to flash a ROM again and simple allow the script to finish and then the tablet will reboot on its own when it is finished with the script. And you will be greeted with your new ROM you just successfully flashed.
Again let me know if I am wrong on assuming you forced a reboot mid install ( aka while u saw all the errors)
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
No, after pushing the TWRP recovery to the Xoom using adp, I would clean install a ROM and get one of two results....1) the ROM would run for a few seconds and then reboot, or 2) the ROM would run, but everything would fc. Fixing permissions, wiping everything, etc., wouldn't help the issue. No matter what I tried under TWRP, those were the results. I ended up having to start from scratch to negate whatever it was that was making the xoom go funky. Once I pushed rogue and followed the same process, I was back in business.
Sent from my Xoom using Tapatalk 2
Having not learnt my lesson from previous Android adventures, I decided update CyanogenMod installation from 10.1.3 to 10.2.0 on my Nexus S. I did the sideload from ClockworkMod recovery, rebooted, and got stuck on the loading screen. Having read suggestions to update GApps as well, I went back into ClockworkMod recovery, sideloaded the GApps, and, again, no joy. I understand that the next step to recover the phone is to factory reset it, but I forgot to backup everything beforehand.
I have some important information that I really don't want to lose in a factory reset. Complicating matters is that I've turned on encryption, so I can't simply use the ClockworkMod backup system and/or access the SD card. I'm running Linux with adb, so I can shell in if someone tells me how to dump the saved data off the phone. Even if I just get raw data and I have to enter it back in myself, that's better than losing it.
I know that downgrading back to 10.1 without a wipe is generally frowned upon. Is it worth gambling with the 10.3 nightlies to see if I can get a stable Android (there's an oxymoron!) boot going long enough for me to get everything off my phone before wiping it and reverting back to 10.2? If the issue is a corrupted apk, can I manually remove them to figure out what the problem is?
Borden Rhodes said:
Having not learnt my lesson from previous Android adventures, I decided update CyanogenMod installation from 10.1.3 to 10.2.0 on my Nexus S. I did the sideload from ClockworkMod recovery, rebooted, and got stuck on the loading screen. Having read suggestions to update GApps as well, I went back into ClockworkMod recovery, sideloaded the GApps, and, again, no joy. I understand that the next step to recover the phone is to factory reset it, but I forgot to backup everything beforehand.
I have some important information that I really don't want to lose in a factory reset. Complicating matters is that I've turned on encryption, so I can't simply use the ClockworkMod backup system and/or access the SD card. I'm running Linux with adb, so I can shell in if someone tells me how to dump the saved data off the phone. Even if I just get raw data and I have to enter it back in myself, that's better than losing it.
I know that downgrading back to 10.1 without a wipe is generally frowned upon. Is it worth gambling with the 10.3 nightlies to see if I can get a stable Android (there's an oxymoron!) boot going long enough for me to get everything off my phone before wiping it and reverting back to 10.2? If the issue is a corrupted apk, can I manually remove them to figure out what the problem is?
Click to expand...
Click to collapse
1. why are you side loading instead of flashing normal?
2. have you tried wiping everything minus sd and data and returning to 10.1.3?
3. when jumping versions, you need a full wipe..
Setting.Out said:
1. why are you side loading instead of flashing normal?
Click to expand...
Click to collapse
I sideload the update because you can't access an encrypted SD Card (which mine is) from recovery mode. I'm not aware of any other way to do upgrades.
Setting.Out said:
2. have you tried wiping everything minus sd and data and returning to 10.1.3?
Click to expand...
Click to collapse
Is there a way to do this? My understanding is that a wipe will clear the data and the SD Card unless you're lucky. If I could revert back to 10.1.3 without touching the data, that would be great, but I'd want to be linked to a tutorial so I'm sure not to mess up.
Setting.Out said:
3. when jumping versions, you need a full wipe..
Click to expand...
Click to collapse
Yeah, I'm an idiot. I've gotten away with sideload updates in the past, but Android caught me this time and left me in limbo.
Borden Rhodes said:
I sideload the update because you can't access an encrypted SD Card (which mine is) from recovery mode. I'm not aware of any other way to do upgrades.
Is there a way to do this? My understanding is that a wipe will clear the data and the SD Card unless you're lucky. If I could revert back to 10.1.3 without touching the data, that would be great, but I'd want to be linked to a tutorial so I'm sure not to mess up.
Yeah, I'm an idiot. I've gotten away with sideload updates in the past, but Android caught me this time and left me in limbo.
Click to expand...
Click to collapse
If you boot into CWM and do a format/wipe on everything MINUS the SD and DATA, you won't lose anything, but it may not fix your issue.. If you get your phone back up and running take off the encryption and back up your files, FULL WIPE and try again..
Thank you for the quick reply.
Setting.Out said:
If you boot into CWM and do a format/wipe on everything MINUS the SD and DATA, you won't lose anything, but it may not fix your issue.. If you get your phone back up and running take off the encryption and back up your files, FULL WIPE and try again..
Click to expand...
Click to collapse
When I go into ClockwordMod, version 6.0.4.3, the 'wipe data/factory reset' is the only option that I see, but it then warns me that all data will be wiped, which, I'm guessing, includes the /data partition. Is this correct or should I look some place else?
Borden Rhodes said:
Thank you for the quick reply.
When I go into ClockwordMod, version 6.0.4.3, the 'wipe data/factory reset' is the only option that I see, but it then warns me that all data will be wiped, which, I'm guessing, includes the /data partition. Is this correct or should I look some place else?
Click to expand...
Click to collapse
Mounts and storage / format
Sent from my Nexus S using XDA Premium 4 mobile app
---------- Post added at 11:34 PM ---------- Previous post was at 11:31 PM ----------
Also go to advanced / wipe dalvik... Are you sure you've flashed Roms before?
Sent from my Nexus S using XDA Premium 4 mobile app
Setting.Out said:
Mounts and storage / format
Click to expand...
Click to collapse
OK, found it there, and formatted /storage, /cache, /boot, and /system. Reflashed CM 10.2 and GApps 4.3 with no success. However, I did manage to dd dump the contents of mmcblk0p2 and mmcblk0p3 to my Linux hard drive, so if I ever figure out how to mount those images in Linux, I should be able to recover everything.
Setting.Out said:
Also go to advanced / wipe dalvik
Click to expand...
Click to collapse
Yep, I did that, too.
Setting.Out said:
... Are you sure you've flashed Roms before?
Click to expand...
Click to collapse
I don't understand this question. How else could I have gotten CM onto my phone in the first place if I never flashed a ROM?
With few other options, I did a factory reset which, predictably, wiped everything but the SD card and put me into a fresh phone. It's also not mounting the SD. So, since all of my data on my phone is gone, I'll just have to hang onto the dumps that I have and hope and pray that someone can tell me how to mount them to get all of my files back.