Database Info

[Q] Unable to mount /fat. What are my options?

Alright guys, I hate to do this. I've been messing around with this stuff for years now, but I'm still an amateur compared to most everybody around here. I've messed up a lot of phones and have been able to pull them from the brink before through a combination of google-fu and dumb luck. This time I haven't been able to do it yet after about 10 hours of work. Here's the rundown:
Had a stock HTC One S (T-mobile and updated OTA to jellybean) until yesterday.
Unlocked the bootloader the official HTC way.
Got root access.
Flashed TWRP 2.5(hopefully the right version)
Flashed a Rom
Bootloop
Mess with stuff, wipe some things, reflash, but still bootloop. No recovery.
Here's where I am now:
I can get into the bootloader and recovery and I have fastboot access.
I can push files in adb and do whatever with fastboot.
Now here is where I am stuck. Every time I try to wipe, flash or anything I get the message E:Unable to mount /fat
I would love some help from anybody on this. I have searched high and low for the same problem but came back empty handed except for feeling that it has something to do with partitioning.

srk10 said:
Alright guys, I hate to do this. I've been messing around with this stuff for years now, but I'm still an amateur compared to most everybody around here. I've messed up a lot of phones and have been able to pull them from the brink before through a combination of google-fu and dumb luck. This time I haven't been able to do it yet after about 10 hours of work. Here's the rundown:
Had a stock HTC One S (T-mobile and updated OTA to jellybean) until yesterday.
Unlocked the bootloader the official HTC way.
Got root access.
Flashed TWRP 2.5(hopefully the right version)
Flashed a Rom
Bootloop
Mess with stuff, wipe some things, reflash, but still bootloop. No recovery.
Here's where I am now:
I can get into the bootloader and recovery and I have fastboot access.
I can push files in adb and do whatever with fastboot.
Now here is where I am stuck. Every time I try to wipe, flash or anything I get the message E:Unable to mount /fat
I would love some help from anybody on this. I have searched high and low for the same problem but came back empty handed except for feeling that it has something to do with partitioning.
Click to expand...
Click to collapse
not sure but it can be possible that some partitions are damaged.
run the latest ruu to restore all the partitions.
twrp 2.5.0.0 have some problems with custom roms,
try twrp 2.3.3.0, it seems that this version has mostly no problems with flashing roms.
do not forget to flash the boot.img after flashing the rom or you will get a bootloop.
before flashing a rom wipe 3x system 3x data 3x cache to be sure that your phone is clean of old system stuff.
here is the link for twrp 2.3.3.0
https://www.dropbox.com/s/pvspwkekl42zkqa/openrecovery-twrp-2.3.3.0-ville.img

Thanks so much for the reply. I downgrade to twrp 2.3 and managed to use the windows utility to reformat my sd card. Wasn't sure that wasn't going to shoot me in the foot, but it worked and I am back in business with a phone that boots.

[Q] Can't Get Rom to Boot

I was able to get my wife's phone unlocked over the weekend. I threw twrp 2.5.0.0 on there and tried to flash cleanrom. The phone was on the newest bootloader, so I tried flashing the boot.img in fastboot. It just stays on the boot screen forever. I found that there may be issues with newer twrp versions so I tried installing 3 different older version of twrp and all were unresponsive to touch. I could press power once and the twrp lock screen would come up, but that was it. I put 2.5.0.0 back on and it became usable again. Unfortunately I'm not S-Off yet because it says you have to be rooted and my plan was to put CleanRom on and then S-Off. I've verified the MD5 of the ROM zip on the phone. When I am going through the rom install though, and I go through all the options and it starts to install, it literally takes a tenth of a second and says successful. Then when I go to reboot to bootloader, it asks me if i'm sure since i don't have an OS installed. I figured that's just because I haven't flashed the boot img yet, but I am used to rom installs taking a couple seconds on my One XL. I've tried installing the boot.img with Hasoon's all-in-one and it says successful. I've tried installing the bulletproof kernel both via zip format and the boot img and still nothing boots up. What else can I try guys? The wife goes out of town tomorrow morning and needs a working phone. Thanks for your help.
edit: i found the log of the cleanrom install which appears to show the install failing.

utdps said:
I was able to get my wife's phone unlocked over the weekend. I threw twrp 2.5.0.0 on there and tried to flash cleanrom. The phone was on the newest bootloader, so I tried flashing the boot.img in fastboot. It just stays on the boot screen forever. I found that there may be issues with newer twrp versions so I tried installing 3 different older version of twrp and all were unresponsive to touch. I could press power once and the twrp lock screen would come up, but that was it. I put 2.5.0.0 back on and it became usable again. Unfortunately I'm not S-Off yet because it says you have to be rooted and my plan was to put CleanRom on and then S-Off. I've verified the MD5 of the ROM zip on the phone. When I am going through the rom install though, and I go through all the options and it starts to install, it literally takes a tenth of a second and says successful. Then when I go to reboot to bootloader, it asks me if i'm sure since i don't have an OS installed. I figured that's just because I haven't flashed the boot img yet, but I am used to rom installs taking a couple seconds on my One XL. I've tried installing the boot.img with Hasoon's all-in-one and it says successful. I've tried installing the bulletproof kernel both via zip format and the boot img and still nothing boots up. What else can I try guys? The wife goes out of town tomorrow morning and needs a working phone. Thanks for your help.
edit: i found the log of the cleanrom install which appears to show the install failing.
Click to expand...
Click to collapse
Did you flash boot boot.img?

Crypto66 said:
Did you flash boot boot.img?
Click to expand...
Click to collapse
I've narrowed down the issue to the install of CleanROM failing. This may be to twrp 2.5.0.0 but as I've said, earlier versions such as 2.3.3.0 aren't responding to touch for some reason. I don't think 2.5.0.0 is my problem though. I can see it if it didn't wipe properly, but the install is failing due to I/O errors.
But yes, I have tried flashing boot.img. twrp tells me I don't have an os when I try to reboot though, so that's the issue.

Try going to the advanced tab and fix permissions.
Sorry for slow responses, I've got to wait 5 minutes in between posts.

Crypto66 said:
Try going to the advanced tab and fix permissions.
Sorry for slow responses, I've got to wait 5 minutes in between posts.
Click to expand...
Click to collapse
Fix permissions won't work without a rom installed. It fails. And from what I understand anyways, fixing permissions is mostly for apps anyways.

Problem solved. Everyone make sure to use TWRP 2.3.3.1 and only that exact version. Older has touchscreen problems and newer has install issues. Man, this stuff can be frustrating at times.

That's not exactly true. Older versions work just fine, I'm using version 2.2 and it has never failed me.
Older versions aren't working for you because you have a newer touchscreen firmware, you would need to downgrade your touchscreen firmware in order to have touch response. For the same reason, you would not be able to run aosp roms until downgrading. Just thought I'd clear that up.
Sent from my One XL using XDA Premium

Several Issues related to updating CM and S-Off

I had been needing to update my phone for a few months now, but because I'm super lazy and I have to flash the boot.img with a pc first, I avoided it... until tonight.
First, I had CM10.1 flashed, did my usual thing: dled the latest nightly, extract zip file, wipe, flash boot.img... went to flash nightly (which I noticed only after was 10.2 nightly) and it failed.
I had done a backup before all of this, but restoring the backup does nothing. Stuck at the HTC splash screen with red text.
When I noticed I was trying to update from 4.2.2 to 4.3, I found the thread on here and noticed that to do so, I had to attain S-Off first. I followed the instructions to do so and at the very last step ( adb shell su -c "/data/local/tmp/soffbin3" ), there's an (unwanted) error. It says su directory not found. In the last successful boot I had before all of this, I know debugging was enabled, and I had flashed superuser.zip in TWRP successfully, and I know I had SuperCID. There was also an issue where, when the instructions state the system should boot to android, my phone just turns off. I booted into TWRP and continued the steps...
I got fed up with all of this and just tried to flash CM10.1. Went through all my normal steps, but now the install fails (Error 7). (I tried the trick where you remove some lines of code, but when I try to flash the altered zip, it just fails. No error listed.) I think it's because of the S-Off attempt. (MID is PJ8312000 I THINK... I recognized it from the S-Off process.)
I've tried everything: updated TWRP, switched to CWM, restored backup AGAIN... still stuck. I need help

When you made your backup did you backup boot? And when you restored did you flash that boot?
What ROM were you on when you attempted the s-off process? You said you couldn't get anything to boot, so if you didn't have a bootable ROM installed that's why it failed.
You should really never removed lines of code from an updater script if a ROM won't install, it's stopping it for a reason. Every time I've seen someone do this and the ROM flashed "successfully" it's bricked their phone.
Lastly, cm10.2 doesn't require s-off. It does require you to run the 3.18 RUU first though, and that requires s-off.
Sent from my Evita

timmaaa said:
When you made your backup did you backup boot? And when you restored did you flash that boot?
What ROM were you on when you attempted the s-off process? You said you couldn't get anything to boot, so if you didn't have a bootable ROM installed that's why it failed.
You should really never removed lines of code from an updater script if a ROM won't install, it's stopping it for a reason. Every time I've seen someone do this and the ROM flashed "successfully" it's bricked their phone.
Lastly, cm10.2 doesn't require s-off. It does require you to run the 3.18 RUU first though, and that requires s-off.
Sent from my Evita
Click to expand...
Click to collapse
Hey, thanks for responding!
I can't remember the nightly I was on exactly, but it was definitely CM10.1 (Android 4.2.2). I don't think it's hard bricked. (I can still access bootloader and recovery.)
Do you have any advice on what I could/should do (besides hang myself... :crying...?

vowelsounds said:
Hey, thanks for responding!
I can't remember the nightly I was on exactly, but it was definitely CM10.1 (Android 4.2.2). I don't think it's hard bricked. (I can still access bootloader and recovery.)
Do you have any advice on what I could/should do (besides hang myself... :crying...?
Click to expand...
Click to collapse
Hey, I flashed the boot.img from the nandroid backup then restored. Finally got it working again!
Thanks for the help; please close thread!

Good news. Time to get s-off? If so, I'd suggest temporarily flashing a 4.1 ROM purely for s-off process, many folks have had trouble with it working 4.2 ROMs.
Sent from my Evita

vowelsounds said:
I don't think it's hard bricked. (I can still access bootloader and recovery.)
Click to expand...
Click to collapse
Just for future reference: If the screen comes on for this device, its almost certainly not bricked, and you can recover.
---------- Post added at 11:18 AM ---------- Previous post was at 11:17 AM ----------
vowelsounds said:
Thanks for the help; please close thread!
Click to expand...
Click to collapse
Why do folks always ask for their threads to be closed the second they resolve their problem? Its not your decision to make. Threads stay open, in case others want to make further comments or ask their own questions.
The only time threads on XDA get closed typically, is if there is some kind of excessive fighting/conflict, or rules have been broken.

[Q] Need some help, unable to flash roms

Ok so my m8 from Verizon which has an unlocked bootloader, s-off, and is rooted with TWRP flashed and working but is unable to flash roms. I first tired to flash ViperONE but it said it failed with a status reason 7, ok thats fine lets reboot to the system, oh wait it's stuck on the white background green htc text logo. so I'm able to RUU back to stock and try to install cleanrom 1.0, failed, ok lets reboot back to system, oh wait stuck again, had to RRU back and now I don't know what the hell is going on with my phone. root checker verified root, when i boot into bootloader it says its unlocked and s-off, why can't i flash roms?
I did the weaksauce temproot and firewater exploit to get s-off.

Did you perm root?

Bellypock said:
Did you perm root?
Click to expand...
Click to collapse
Yea I did, so I uninstalled just to be safe and now when I try to reflash supersu.zip through recovery it flashes ok, but then when I boot back into the OS superuser is not installed.

ok im posting back becuase the issue has been resolved. I guess I had a corrupted copy of twrp because I flashed Philz touch recovery and everything flashed perfectly.

nfrederick said:
ok im posting back becuase the issue has been resolved. I guess I had a corrupted copy of twrp because I flashed Philz touch recovery and everything flashed perfectly.
Click to expand...
Click to collapse
I am still having the same issue. I can't flash any ROM. I get the Status 7 issue when flashing ViperOne. I have tried TWRP, CWM, and Philz, and I can't flash a ROM with any of them. How are you flashing your Recovery? I am wondering if flashing Recovery using Flashify is part of my problem. I this point, I am searching for any answer to this problem. I have been trying to flash a ROM since April 26th. Let me know. Thanks.
Rob

Error: Cannot open recovery

Ok, here's some background on my device:
I s-off'ed using firewater method, it worked fine
I flashed CWM through Fastboot, and then flashed a supersu zip through CWM.
After this, I made a nandroid and flashed to a GPE rom to try it out, decided i wanted to give sense 6 a longer chance, so I restored my Nandroid.
Then the OTA update came along, and annoyed me to install it for awhile. So I decided to try to, so I flashed the stock recovery from this thread. It did not flash.. After changing the usb cable and usb port, and a few days.. it worked.. maybe
When I boot into recovery, i get the little picture of the phone with the red triangle and exclamation point (that I think is stock recovery)
but when I try to install the OTA, it looks like it's working, except about a third of the way through (according to the green bar on the bottom) it goes straight to the red triangle and exclamation point. After about 5 minutes (not sure exactly) it reboots and nothing is changed. A bit later, it'll bug me again to update.
Now, I tried to flash both CWM and TWRP, and both result in "Error: Cannot open recovery '[recoveryname.img]'"
I have tried it with both CWM and TWRP, on two different machines, both running OSX Mavericks... Same results for all of them.
Earlier today, I factory reset, yet it still doesn't work. Anybody have any advice?

Alright, well I have no idea why this worked, but I tried flashing TWRP through the ROM manager app, and that worked. I feel rather stupid for not trying this earlier..
anyway, I'm good now

Dwight Caffery said:
Alright, well I have no idea why this worked, but I tried flashing TWRP through the ROM manager app, and that worked. I feel rather stupid for not trying this earlier..
anyway, I'm good now
Click to expand...
Click to collapse
Glad all is well.
I would get in the habit with S-OFF to never take an OTA..even when confirmed ok for rooters.
eventually someone WILL pull the OTA, and the firmware will be flashable for those on S-OFF like this most recent OTA.
Simply fastboot the said OTA firmware and save yourself a bunch of hassel.
Happy flashing