Database Info

AT&T Htc One X - Bricked and need advice

One of my friends BRICK his phone and he has no idea how. He has a rooted HTC ONE X on AT&T network with Viper XL (Not even sure what version of the ROM) probably from last december.
It is now stuck on the Booting animation screen and won't get passed that. I am able to access TWRP recovery, but there is not zip files or backups any longer. When I originally flashed this phone for him I had a zip file on the root of the internal SD CARD. It no longer is there and i have not rooted/flashed a phone for almost a year and can't remember.
I tried to fastboot oem lock and it fails (was thinking i could some how get it to boot and install stock jelly bean)
I am able to mount the SD card via TWRP and throw a rom in there via zip, but when i unmount i and go to restore or install i do not see any zip. When I mount again the file i put in the phone no longer exists.
Is there a work around or another way to flash any custom room. I was thinking of CM10 nightly evita... I don't care what rom as long as i can get the phone working again for him.
Is there a way to flash a rom the way we flash boot.img via fastboot where the files can reside on the PC and not the phone? Any assistance/tips would be great. Again i don't care which rom I flash and i have TWRP recovery access. Currently i have CM10 downloaded if hat helps. Thank you in advanced

Is there anything showing up on the sd card at all in TWRP? You could try formatting the sd card in Windows and trying to move a ROM over again.
Sent from my Evita

timmaaa said:
Is there anything showing up on the sd card at all in TWRP? You could try formatting the sd card in Windows and trying to move a ROM over again.
Sent from my Evita
Click to expand...
Click to collapse
Im able to see folders and stuff like the typical android folders. So you are saying i should mount the SD card/try to format the sd card via windows then try to put a zip file in there to see if i can access it? Question.. All i would need to do is flash the boot.img first via fastboot then install the zip via twrp right?

Yeah that's what I mean. Most people flash the boot.img afterwards but I believe you can do it before flashing the ROM.
Sent from my Evita

timmaaa said:
Yeah that's what I mean. Most people flash the boot.img afterwards but I believe you can do it before flashing the ROM.
Sent from my Evita
Click to expand...
Click to collapse
When i format the sd card does it need to be FAT32? What format?

Yep, fat32 is the right format.
Sent from my Evita

timmaaa said:
Yep, fat32 is the right format.
Sent from my Evita
Click to expand...
Click to collapse
Weird i get the same results as before. I formatted the SD card via fat32, through the zip in there, then I unmount the sd card so i can get back to twrp menus to install and android folders are back, but no zip. I am able to successfully copy the cm10 zip there so i don't get it.

Which version of TWRP are you using? And what process are you following when wiping before the flash?
Sent from my Evita

Sounds similar to what happened to me when i did factory reset in bootloader. Others seem to be able to just format in pc and have it work in recovery but it didn't work for me so i just ruu'd to fix it. Since it might have been awhile since you setup his phone you might as well s-off the phone then run latest jb ruu so you have flash latest cm10.1 nightlies which also no longer needs touchscreen downgrade. Afterwards flash latest twrp 2.6.0.0 and copy rom of choice to sdcard and flash.

How will he s-off if he can't boot into the OS?
Sent from my Evita

timmaaa said:
Which version of TWRP are you using? And what process are you following when wiping before the flash?
Sent from my Evita
Click to expand...
Click to collapse
TWRP version 2.3.1.0
Weird I never had issues before and fyi this phone used to be mine so i did all the flashing originally then sold it to a friend of mine and he refused to go back to stock and preferred to stay with viper xl. Now i'm trying to help him out, any thoughts?

DvineLord said:
Sounds similar to what happened to me when i did factory reset in bootloader. Others seem to be able to just format in pc and have it work in recovery but it didn't work for me so i just ruu'd to fix it. Since it might have been awhile since you setup his phone you might as well s-off the phone then run latest jb ruu so you have flash latest cm10.1 nightlies which also no longer needs touchscreen downgrade. Afterwards flash latest twrp 2.6.0.0 and copy rom of choice to sdcard and flash.
Click to expand...
Click to collapse
That's the problem I downloaded the latest RUU from HTC and I don't have a way to flash it or else I would have. Not sure what else I can do here. Anyone have any ideas what I can try next or is this consider a Permanently bricked phone? If it is then i don't want to spend time on it as I have already dedicated over 2 hrs, thanks.

XsMagical posted a fix for corrupted sd cards on this forum a while back, you could give that a try.
Sent from my Evita

timmaaa said:
XsMagical posted a fix for corrupted sd cards on this forum a while back, you could give that a try.
Sent from my Evita
Click to expand...
Click to collapse
So that's what it probably is a corrupted SD CARD? Thanks I will search his posts.

Yeah that's my best guess. It does seem odd that you can still view the Android folders from within recovery though. When you copy something from your pc across does it definitely succeed? I had a wild thought earlier that maybe it had been formatted as read only or something like that.
Sent from my Evita

timmaaa said:
Yeah that's my best guess. It does seem odd that you can still view the Android folders from within recovery though. When you copy something from your pc across does it definitely succeed? I had a wild thought earlier that maybe it had been formatted as read only or something like that.
Sent from my Evita
Click to expand...
Click to collapse
Yeah it successfully completes and I am able to see the file there. Even if i remove the USB cable without unmounting and then plug it back the file is still there. It's when I unmount from TWRP when it then vanishs. I found the article from the guy who wrote a tutorial on how to fix corrupted SD cards, but the link is now broken and no longer exists, doh!

Have you tried upgrading to TWRP 2.6? Not sure if it's gonna help, but anything is worth a try at this stage, right?
Sent from my Evita

timmaaa said:
Have you tried upgrading to TWRP 2.6? Not sure if it's gonna help, but anything is worth a try at this stage, right?
Sent from my Evita
Click to expand...
Click to collapse
Sure it's worth a try. How do i upgrade twrp? It's been a while. Is it just flashing via fastboot? BC if it's a zip remember I can't do that.

Download it from here. Put it in your fastboot folder. Issue these fastboot commands:
fastboot flash recovery "recovery.img"
(whatever the exact filename is, minus the talking marks)
fastboot erase cache
fastboot reboot-bootloader
Now you can enter recovery from your phone screen.
Sent from my Evita

timmaaa said:
Download it from here. Put it in your fastboot folder. Issue these fastboot commands:
fastboot flash recovery "recovery.img"
(whatever the exact filename is, minus the talking marks)
fastboot erase cache
fastboot reboot-bootloader
Now you can enter recovery from your phone screen.
Sent from my Evita
Click to expand...
Click to collapse
Great thanks.

[Q] Upgrade CM from stable CM10 to latest on HTC One S TMO

Hi -
I have an HTC One S (unlocked and rooted - t-mobile) running cm-10.0.0-ville - This is the last stable CyanogenMod ROM.
I would greatly appreciate it if someone could walk me through the steps on how to upgrade this to another ROM (of your choice) that will give me Android 4.3 - There are some features in 4.3 OS that I would love to have (very practical)...
I have heard that I would have to flash boot.img manually using adb if I were to install another ROM. I am worried I will miss a step and soft or hard brick my phone during the process.... I am familiar with Samsungs but HTC from my experience is a hit or miss when it comes to upgrading ROMS or flashing new ones...
Please help so I dont end up with 'unable to mount sdcard' type errors

DroidLuvver said:
Hi -
I have an HTC One S (unlocked and rooted - t-mobile) running cm-10.0.0-ville - This is the last stable CyanogenMod ROM.
I would greatly appreciate it if someone could walk me through the steps on how to upgrade this to another ROM (of your choice) that will give me Android 4.3 - There are some features in 4.3 OS that I would love to have (very practical)...
I have heard that I would have to flash boot.img manually using adb if I were to install another ROM. I am worried I will miss a step and soft or hard brick my phone during the process.... I am familiar with Samsungs but HTC from my experience is a hit or miss when it comes to upgrading ROMS or flashing new ones...
Please help so I dont end up with 'unable to mount sdcard' type errors
Click to expand...
Click to collapse
It's simple. As long as you're S-ON, it's unlikely that you'll head for a permanent brick.
I'd suggest you go for PACman ROM or Odyssey. Both are great.
Steps are simple. I am assuming you have TWRP recovery.
1. Download the ROM.
2. Get SuperWIPE script from PACman Thread.
3. Transfer both of the files to your SD partition. Keep a copy of ROM.zip on PC.
4. Flash the Superwipe script in TWRP recovery first. (won't wipe the SD partition, everything else would be wiped pertaining to the previous ROM)
5. Then flash PAC/Odyssey ROM.zip in TWRP recovery.
6. go to Bootloader, and then to FASTBOOT
7. connect phone to PC. It should say Fastboot USB mode.
8. The ROM.zip you used, Extract BOOT.IMG from it using 7zip/winrar, and place it inside fastboot/adb folder.
9. use the following command to flash boot.img.
Code:
fastboot flash boot boot.img
20. congrats, all done. boot up the ROM.
If you need help on adb/fastboot, head over to the 2nd link in my signature and read the PRE-REQUISITIES and Common Steps part.

khan.orak said:
It's simple. As long as you're S-ON, it's unlikely that you'll head for a permanent brick.
I'd suggest you go for PACman ROM or Odyssey. Both are great.
Steps are simple. I am assuming you have TWRP recovery.
1. Download the ROM.
2. Get SuperWIPE script from PACman Thread.
3. Transfer both of the files to your SD partition. Keep a copy of ROM.zip on PC.
4. Flash the Superwipe script in TWRP recovery first. (won't wipe the SD partition, everything else would be wiped pertaining to the previous ROM)
5. Then flash PAC/Odyssey ROM.zip in TWRP recovery.
6. go to Bootloader, and then to FASTBOOT
7. connect phone to PC. It should say Fastboot USB mode.
8. The ROM.zip you used, Extract BOOT.IMG from it using 7zip/winrar, and place it inside fastboot/adb folder.
9. use the following command to flash boot.img.
Code:
fastboot flash boot boot.img
20. congrats, all done. boot up the ROM.
If you need help on adb/fastboot, head over to the 2nd link in my signature and read the PRE-REQUISITIES and Common Steps part.
Click to expand...
Click to collapse
Thanks - complete/informative/precise response. Exactly what I was looking for.
My phone isn't S-OFF (meaning, it is S-ON) so I will follow your directions to update to Android 4.3 - will try the ROMs you suggested. Before I do anything, I will make a backup of existing CM rom though of course.... My concern, and the reason why I posted here, was that last time when I made a backup of existing ROM, then tried to restore from it, I got "unable to mount sd/card' message that I was not able to fix myself (had to pay someone to get that one fixed) .. I dont want to get burned again so needed precise instructions to be able to go back and forth (to a new ROM as u suggested, then go back to my existing one using backup)

DroidLuvver said:
Thanks - complete/informative/precise response. Exactly what I was looking for.
My phone isn't S-OFF (meaning, it is S-ON) so I will follow your directions to update to Android 4.3 - will try the ROMs you suggested. Before I do anything, I will make a backup of existing CM rom though of course.... My concern, and the reason why I posted here, was that last time when I made a backup of existing ROM, then tried to restore from it, I got "unable to mount sd/card' message that I was not able to fix myself (had to pay someone to get that one fixed) .. I dont want to get burned again so needed precise instructions to be able to go back and forth (to a new ROM as u suggested, then go back to my existing one using backup)
Click to expand...
Click to collapse
SD not being able to mount is the result of formatting it using anything other than stock recovery.
If you happen to face that error again, flash a stock recovery, wipe SD from bootloader and it's good to go.
You can then reflash custom recoveries.
Sent from my Nexus 7 using Tapatalk HD

khan.orak said:
SD not being able to mount is the result of formatting it using anything other than stock recovery.
If you happen to face that error again, flash a stock recovery, wipe SD from bootloader and it's good to go.
You can then reflash custom recoveries.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Ok - so three questions...
1) flash a stock recovery -- pointers on downloading stock recovery for Tmobile/unlocked HTC One S (s4) ?
2) flash a stock recovery - once I have the recovery files, I use adb to push the recovery to the phone or TWRP ? I couldnt use TWRP or clockwork because it didnt even see sd-card...
3) wipe SD from bootloader - do you mean, using adb, issue a command that formats SD card? If so, what is the command?

DroidLuvver said:
Ok - so three questions...
1) flash a stock recovery -- pointers on downloading stock recovery for Tmobile/unlocked HTC One S (s4) ?
2) flash a stock recovery - once I have the recovery files, I use adb to push the recovery to the phone or TWRP ? I couldnt use TWRP or clockwork because it didnt even see sd-card...
3) wipe SD from bootloader - do you mean, using adb, issue a command that formats SD card? If so, what is the command?
Click to expand...
Click to collapse
1. Stock recovery can be found in the forums. It can also be extracted from any Jellybean OTA.zip for any region but intended for S4 device and not an OTA.zip for One S S3. It can be found in Ota.zip\firmware.zip\recovery.img
2. You put the phone in FASTBOOT mode from bootloader and connect to PC, place recovery inside adb folder and issue this command.
Code:
fastboot flash recovery recovery.img
Pretty much similar to boot.img method.
Similarly you can flash custom recoveries
3. When you flash stock recovery, go to bootloader and select CLEAR STORAGE and then FACTORY RESET. That does the job.
Sent from my Nexus 7 using Tapatalk HD

Here is the info on my phone ... (below) - I have an older kernel and in order to upgrade to Android 4.3 (Odyssey or PAC), I will have to upgrade kernel right??
cw v6.0.3.1
VLE PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-1-13.50.05.31
OpenDSP-v31.1.0.45.0015
eMMC-boot
Apr 20 2012, 15:14:18

Can anyone please confirm this method?
This looks great, but I'm wary that no one has confirmed success.
My phone:
VLE PVT SHIP S-ON RL
HBOOT-1.14.0005
RADIO-1.13.50.05.25
OpenDSP-v29.1.0.45.0622
eMMC-boot
Nov 21 2012, 12:17:41
TWRP 2.4.1.0
Currently running CyanogenMod:10.1-20130304-Experimental-ville-M2
(On of the last of the 10.1 ROMs before the updated kernel requirement?)​
So is this a good (confirmed) method for me? Other ideas? Thanks.
khan.orak said:
It's simple. As long as you're S-ON, it's unlikely that you'll head for a permanent brick.
I'd suggest you go for PACman ROM or Odyssey. Both are great.
Steps are simple. I am assuming you have TWRP recovery.
1. Download the ROM.
2. Get SuperWIPE script from PACman Thread.
3. Transfer both of the files to your SD partition. Keep a copy of ROM.zip on PC.
4. Flash the Superwipe script in TWRP recovery first. (won't wipe the SD partition, everything else would be wiped pertaining to the previous ROM)
5. Then flash PAC/Odyssey ROM.zip in TWRP recovery.
6. go to Bootloader, and then to FASTBOOT
7. connect phone to PC. It should say Fastboot USB mode.
8. The ROM.zip you used, Extract BOOT.IMG from it using 7zip/winrar, and place it inside fastboot/adb folder.
9. use the following command to flash boot.img.
Code:
fastboot flash boot boot.img
20. congrats, all done. boot up the ROM.
If you need help on adb/fastboot, head over to the 2nd link in my signature and read the PRE-REQUISITIES and Common Steps part.
Click to expand...
Click to collapse

jeremybagai said:
This looks great, but I'm wary that no one has confirmed success.
My phone:
VLE PVT SHIP S-ON RL
HBOOT-1.14.0005
RADIO-1.13.50.05.25
OpenDSP-v29.1.0.45.0622
eMMC-boot
Nov 21 2012, 12:17:41
TWRP 2.4.1.0
Currently running CyanogenMod:10.1-20130304-Experimental-ville-M2
(On of the last of the 10.1 ROMs before the updated kernel requirement?)​
So is this a good (confirmed) method for me? Other ideas? Thanks.
Click to expand...
Click to collapse
Unrelated to what you asked but can you tell me that if you are running "10.1-20130304-Experimental-ville-M2" do you have 4G/3G connection ?

DroidLuvver said:
Unrelated to what you asked but can you tell me that if you are running "10.1-20130304-Experimental-ville-M2" do you have 4G/3G connection ?
Click to expand...
Click to collapse
4g works, no problem. I have some issue with Widget Locker that makes me reboot every day or so, but other than that it's a nice build.

jeremybagai said:
4g works, no problem. I have some issue with Widget Locker that makes me reboot every day or so, but other than that it's a nice build.
Click to expand...
Click to collapse
Can you tell me what radio you have got?
Sent from my HTC One S using xda app-developers app

DroidLuvver said:
Can you tell me what radio you have got?
1.13.50.05.25
So it sounds like I'm helping you get to an Experimental Cyanogen 10.1 rom without updating your firmware. It should work. Enjoy.
But I wish someone would comment more on your original question -- how best to upgrade firmware and explore the newer 10.1 and 10.2 roms?
Can anyone confirm what method they used?
Jeremy
Click to expand...
Click to collapse

jeremybagai said:
DroidLuvver said:
Can you tell me what radio you have got?
1.13.50.05.25
So it sounds like I'm helping you get to an Experimental Cyanogen 10.1 rom without updating your firmware. It should work. Enjoy.
But I wish someone would comment more on your original question -- how best to upgrade firmware and explore the newer 10.1 and 10.2 roms?
Can anyone confirm what method they used?
Jeremy
Click to expand...
Click to collapse
So my radio is 1-13.50.05.31 - I wonder if I should find and flash 11.13.50.05.25 to get my 4G back ? You got 1.13 HBOOT ?
Click to expand...
Click to collapse

[Q] Same thing, only different.

Okay, I have the same problem as the guy in this thread: https://forum.xda-developers.com/showthread.php?t=2571779&highlight=wiped+all+partitions , but only have a few differences. I now have no sdcard or sdcard\ext partitions... Says zero megs. Thankfully I back my stuff up everytime I sync up to my pc. Anywho, I believe I need to run RUU mode and reinstall ICS factory. Here is what happened: I have had the phone rooted and S-OFF for about a week and have made a few backups. I went into recovery and made another backup. Rebooted into system, saved contacts, and rebooted back into bootloader by accident. Well when I went to hit "recovery" option, I went down one too any times and hit factory reset. Now, when I go into recovery, there is not any restore points, nor any sdcard options available. I cant mount up usb mass storage in TWRP because there is no sdcard partition...Hrmmmmm...... I guess the actual question is, "Do I need to run RUU and that will probably, maybe fix it?"
Tid Bits:
TWRP v2.6.3.0
***tampered***
***unlocked***
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT- 2.14.0000
RADIO- 0.24P.32.09.06
OpenDSP- v34.1.0.45.1219
eMMC-boot

Its a known issue that doing a factory reset in bootloader on a modded EVITA corrupts the SD card. Plug the phone into a Windows PC, go to device manager, find the SD and format it FAT32. Its that simple.
Question 16 in the FAQs: http://forum.xda-developers.com/showthread.php?t=2136172

at which point i should be able to push a rom to the phone and get my OS back, correct? as of right now, i have no OS, but full recovery.

That's right. Format it then copy a ROM across to flash.
Sent from my Evita

Just did that. Had to reflash superSU before flshing a rom. It will not flash the ROM, it says that E: Error executing updater binary in zip 'blah, blah,blah' It did this with the last ROM i tried flashing. Any ideas?

lil_phreek said:
Just did that. Had to reflash superSU before flshing a rom. It will not flash the ROM, it says that E: Error executing updater binary in zip 'blah, blah,blah' It did this with the last ROM i tried flashing. Any ideas?
Click to expand...
Click to collapse
What ROM are you trying to flash, and what recovery are you using?
Sent from my One X using XDA Premium 4 mobile app

TWRP 2.6.3
Illusion 4.4.2

lil_phreek said:
TWRP 2.6.3
Illusion 4.4.2
Click to expand...
Click to collapse
Are you using the modified version of 2.6.3.0? The official version won't flash 4.4 ROMs. Also, there's no need to flash any Superuser zip, but if there was you'd need to flash it after the ROM.
Sent from my Evita

lil_phreek said:
TWRP 2.6.3
Illusion 4.4.2
Click to expand...
Click to collapse
There have been multiple reports in that thread of failed flashings with the unofficial twrp. There are some CWM versions available for 4.4 Roms though. I think the first few pages of the Beanstalk thread should get you going with that.
Sent from my One X using XDA Premium 4 mobile app

"wishing I was Kenny right now" My mistake on not paying attention to the fine print....I will check out that other thread. Thanks. I will post in a bit and let you guys know how it works out for me.

Don't forget to click the "Thanks" button for any posts that you found helpful.

Sorry for the delay guys. Literally as soon as I got my phone fixed, my laptop, which I use for all my necessary phone needs, slowly closed all its windows down, shut off, and mysteriously lost its OS.... LOL, one thing fixed, another down. Oh well. Anyway, I did exactly as was said in the other thread, and it worked like a charm. I am currently running Beanstalk 4.4, and it is an amazing rom. Love it. And thanks for all the help. I am heading back over to the Infuse forum to try and fix the other phone....

Need urgent help! Bricked for 2 days already!

I successfully rooted and achieved an unlocked bootloader with S-OFF on my Verizon HTC One M8 and also flashed TWRP 2.7.0.2. I downloaded a rom (without an SD card). I booted into recovery and i made a backup (not noticing that one of the lines read "unable to mount '/system". I then wiped and attempted to flash the rom only to find out that i can't find it in my file system. So i put the rom on an SD card and mounted it and tried to flash it, i get this message:
E: Unable to mount '/system'
E: Unable to open zip file.
Error Flashing zip '/external_sd/Roms?ViperOneM*_1.2.0.zip'
Updating partition details...
E: Unable to mount '/system'
So i'm stuck with a boot loader, an unmountable file system, and unable to flash a rom.
I've tried Fix permissions, I've tried mounting the "system" but all that mounts is 'cache' 'data' and 'micro SDcard'.
I hope my nerves are getting the best of me and i can't see something that's right in front of me!
Edit: Flashed CWM Recovery. Trying to install ROM from SD Card results in "Installation Aborted". When i try to side load it hangs at 81%.

Did you flash TWRP using terminal emulator mode as described on the official website for 2.7.0.2? If so you overwrote the system partition. Try flashing the recovery using the fastboot method as this will put the recovery in the right place. Then boot into the bootloader, choose recovery. I think this will get you TWRP in the recovery partition. Once there try flashing a ROM (although o would suggest something closer to stock like Skyfall).
I think what is happening is since the instructions for flashing TWRP via terminal emulator list the wrong partition, when you boot up to system it seems like you are booting to recovery because TWRP shows up. But you're actually on the system partition so when you try to flash a ROM you get an error because you can't mount the partition you're in.
I'm far from an expert in any of this so anyone who is please correct me.

dsEVOlve said:
Did you flash TWRP using terminal emulator mode as described on the official website for 2.7.0.2? If so you overwrote the system partition. Try flashing the recovery using the fastboot method as this will put the recovery in the right place. Then boot into the bootloader, choose recovery. I think this will get you TWRP in the recovery partition. Once there try flashing a ROM (although o would suggest something closer to stock like Skyfall).
I think what is happening is since the instructions for flashing TWRP via terminal emulator list the wrong partition, when you boot up to system it seems like you are booting to recovery because TWRP shows up. But you're actually on the system partition so when you try to flash a ROM you get an error because you can't mount the partition you're in.
I'm far from an expert in any of this so anyone who is please correct me.
Click to expand...
Click to collapse
I did flash TWRP as described. I used Terminal from my Macbook. I did some researching and i did try flashing using the fast boot method. I'm just so stumped!

First of all you aren't bricked. Have you tried using side load to flash the ROM? Try flashing another recovery too.
Sent from my HTC6525LVW using Tapatalk

SimplyNando said:
I did flash TWRP as described. I used Terminal from my Macbook. I did some researching and i did try flashing using the fast boot method. I'm just so stumped!
Click to expand...
Click to collapse
The above suggestion to try and Sideload the ROM install is a good idea. Basically, put the ROM zip file in your platform-tools folder of adb. Then boot to TWRP recovery, choose "sideload" and then issue the command "adb sideload [filename.zip]" (Instructions are found HERE.)
If that doesn't work, have you tried flashing Clockwork Recovery? You may have better luck with that in regards to mounts and/or flashing the ROM...

There's always USB OTG as well
Sent from my HTC6525LVW using Tapatalk

I found THIS thread (for ASUS Transformer though).
What may have happened (if I'm reading the above thread correctly) is that your /system doesn't exist.
Taking a complete stab at a fix, you may be able to use fastboot to flash a working "system.img" file. (Anyone with more expertise, please confirm or refute this...)
EDIT: Found THIS post in the "Official" TWRP release 2.7.0.0 thread I wonder if perhaps this is what happened to you?

WorldOfJohnboy said:
I found THIS thread (for ASUS Transformer though).
What may have happened (if I'm reading the above thread correctly) is that your /system doesn't exist.
Taking a complete stab at a fix, you may be able to use fastboot to flash a working "system.img" file. (Anyone with more expertise, please confirm or refute this...)
EDIT: Found THIS post in the "Official" TWRP release 2.7.0.0 thread I wonder if perhaps this is what happened to you?
Click to expand...
Click to collapse
That does seem like it could be the problem. I just flashed CWM recovery instead but it's still the sam problem. Still can't flash a rom, i also tried using sideboot.

SimplyNando said:
That does seem like it could be the problem. I just flashed CWM recovery instead but it's still the sam problem. Still can't flash a rom, i also tried using sideboot.
Click to expand...
Click to collapse
You might have to find a factory image, an RUU I am not sure if one exists but it will write the partitions. I think somehow your actual system partition was erased which is why it cannot be mounted. Pretty much, your only hope is an RUU or a zipped factory image.

123421342 said:
You might have to find a factory image, an RUU I am not sure if one exists but it will write the partitions. I think somehow your actual system partition was erased which is why it cannot be mounted. Pretty much, your only hope is an RUU or a zipped factory image.
Click to expand...
Click to collapse
I wouldn't be able to get that from the system dump located http://forum.xda-developers.com/showthread.php?t=2695171 ? Is there any other possible explanation??

SimplyNando said:
I wouldn't be able to get that from the system dump located http://forum.xda-developers.com/showthread.php?t=2695171 ? Is there any other possible explanation??
Click to expand...
Click to collapse
no because it is not a flashable zip. Factory image or RUU means the bootloader will literally write the partition. Recovery will mount the partition and write information to it. It cannot create the partition itself which I think is your issue.

Assuming your recovery is fine..this is what I did to fix my self inflicted "soft brick" on Saturday...I mistakenly hit format system instead of just data and cache while trying to start over.
I am running cwm 6047..and for whatever reason the sideload failed with an error trying to sideload flash sky fall.
So I did an adb push skyfall.zip /sdcard/0 and was then able to flash the zip from internal storage.
Hope that helps with your situation.

bakemcbride21 said:
Assuming your recovery is fine..this is what I did to fix my self inflicted "soft brick" on Saturday...I mistakenly hit format system instead of just data and cache while trying to start over.
I am running cwm 6047..and for whatever reason the sideload failed with an error trying to sideload flash sky fall.
So I did an adb push skyfall.zip /sdcard/0 and was then able to flash the zip from internal storage.
Hope that helps with your situation.
Click to expand...
Click to collapse
Yep. You have a bad download. Download a new ROM on your computer...boot to recovery and do a adb sideload or push
Sent from my HTC One M8

Just had a thought... did you flash the insecure Kernel (found HERE) ever? You may not have a writeable /system?
Flash the Kernel, then reflash the official TWRP (both in Fastboot) and see if that works...

WorldOfJohnboy said:
Just had a thought... did you flash the insecure Kernel (found HERE) ever? You may not have a writeable /system?
Flash the Kernel, then reflash the official TWRP (both in Fastboot) and see if that works...
Click to expand...
Click to collapse
Kernel runs inside the rom and the system becomes writeable in the ROM so that won't do anything. I'm pretty convinced he is missing the partition.
Sent from my HTC6525LVW using Tapatalk

Hi did you manage to sort this issue out as i'm having the same issue. it won't install backups or open zip files of the rom's. no matter what i do it won't flash the rom's. i've tried side loading on both cwm and TWRP - as i just said swapped from both recoveries. Managed to mount the sd card and put a new rom on it but won't flash from there and I've tried to move it to internal but fails.
I can't find my stock recovery an a nandroid back up either. Any help would be great
thanks
---------- Post added at 06:34 PM ---------- Previous post was at 06:33 PM ----------
Oh it does let me flash a Kernal zip tho?

jerico9 said:
Hi did you manage to sort this issue out as i'm having the same issue. it won't install backups or open zip files of the rom's. no matter what i do it won't flash the rom's. i've tried side loading on both cwm and TWRP - as i just said swapped from both recoveries. Managed to mount the sd card and put a new rom on it but won't flash from there and I've tried to move it to internal but fails.
I can't find my stock recovery an a nandroid back up either. Any help would be great
thanks
---------- Post added at 06:34 PM ---------- Previous post was at 06:33 PM ----------
Oh it does let me flash a Kernal zip tho?
Click to expand...
Click to collapse
did you try formatting internal yet?

Just for anyone withthe same issue. It ended up being not dnough memory to flash the recovery or the new rom....deerrrrrrr!!!
Haha, cant believe it had me stumped for 5 days trying everything and anything. Formatting would have helped aswell So thanks for the suggestion

jerico9 said:
Just for anyone withthe same issue. It ended up being not dnough memory to flash the recovery or the new rom....deerrrrrrr!!!
Haha, cant believe it had me stumped for 5 days trying everything and anything. Formatting would have helped aswell So thanks for the suggestion
Click to expand...
Click to collapse
I have an HTC version of fastboot/adb that will work on a low memory pc. It's posted in my ruu thread.

dottat said:
I have an HTC version of fastboot/adb that will work on a low memory pc. It's posted in my ruu thread.
Click to expand...
Click to collapse
I mean the device memory was low, so couldn't flash as no room on the device

Need help in restoring to stock htc one mini

I had a rooted htc one mini then i tried changing the firmware to ViperOne but I forgot to boot the boot.img before installing ViperOne through Clorckworkmod recovery. I continued the install then now im always stuck on the booting screen, I tried restoring my backup in Clockworkmod recovery but it always says "E: can't mount sdcard", it kept on saying "can't mount sdcard" on everything in clockworkmod. I also cant access the internal storage thourgh my pc. I have no idea what to do now, tried fixing with RUU but i cant find the one the matches my phone, please help give me the easiest way cause im still a beginner, i dont mind if its rooted or not when its fixed i just want it to work again
Thank you in advance

radster12795 said:
I had a rooted htc one mini then i tried changing the firmware to ViperOne but I forgot to boot the boot.img before installing ViperOne through Clorckworkmod recovery. I continued the install then now im always stuck on the booting screen, I tried restoring my backup in Clockworkmod recovery but it always says "E: can't mount sdcard", it kept on saying "can't mount sdcard" on everything in clockworkmod. I also cant access the internal storage thourgh my pc. I have no idea what to do now, tried fixing with RUU but i cant find the one the matches my phone, please help give me the easiest way cause im still a beginner, i dont mind if its rooted or not when its fixed i just want it to work again
Thank you in advance
Click to expand...
Click to collapse
How did you get Viper for the Mini???
These are likely the instructions for you, too.
http://forum.xda-developers.com/htc-one-mini/help/help-installing-stock-rom-htc-one-mini-t2959490

jollywhitefoot said:
How did you get Viper for the Mini???
These are likely the instructions for you, too.
http://forum.xda-developers.com/htc-one-mini/help/help-installing-stock-rom-htc-one-mini-t2959490
Click to expand...
Click to collapse
tried adb push the zip file but it kept saying adb is out of date, device not found.
UPDATE!
made it work kept loading foe a long time then protocol failure, what does that mean?

radster12795 said:
tried adb push the zip file but it kept saying adb is out of date, device not found.
UPDATE!
made it work kept loading foe a long time then protocol failure, what does that mean?
Click to expand...
Click to collapse
I think you have usb issues. You should either try working from a fresh install of Windows or Ubuntu from disc.
Here are instructions for booting to Ubuntu from disc:
http://forum.xda-developers.com/showpost.php?p=55070544&postcount=22

jollywhitefoot said:
I think you have usb issues. You should either try working from a fresh install of Windows or Ubuntu from disc.
Here are instructions for booting to Ubuntu from disc:
http://forum.xda-developers.com/showpost.php?p=55070544&postcount=22
Click to expand...
Click to collapse
Finally made it work, went to sdcard installed the zip it said successful then i rebooted it but it is still stuck in the booting screen -_-
and when i opened the bootloading screen it still says no OS
TAMPERED
UNLOCKED
M4_UL PVT SHIP S-ON RL
HBOOT-2.21.0000
RADIO-1.27.40e.00.11
OpenDSP-v19.2.0268.0927
OS-
eMMC-boot 1024mb
i think my phone doesnt have the firmware cause it said successful but it also said cant moutn /system at the end, any idea?
Thank you very much btw, for helping me, learned so much stuff
followed the other comments to install the sense6 firmware, my phone needs to be S-OF and superCID, finished superCID but i cant run rumrunner cause my phone dont have OS, is there a way to run rumrunner thourgh fastboot or recovery?

Dude. You have to use files intended for the mini. Install a recovery for the mini from here: http://techerrata.com/browse/twrp2/m4ul and then flash the Rom again

jollywhitefoot said:
Dude. You have to use files intended for the mini. Install a recovery for the mini from here: http://techerrata.com/browse/twrp2/m4ul and then flash the Rom again
Click to expand...
Click to collapse
oaky, i have installed twrp 2.7.1.1 and now adb pushing the rom and ill try to recovery install the rom again
Finished the zip install
Updating partition details...
E:Unable to mount '/system'
Full SELinux support is present.
Installing 'sdcard/Stock_Sense6M4_Deodexed-Rooted.zip'...
Checking for MD5 file..
Skipping MD5 check: no MD5 file found
->Mounting System & Data
->Extracting System
->Extracting Data
->Creating toolbox symlinks
->Creating additional symlinks
->Installing busybox
->Setting permissions
->Extracting kernel
Updating partition detail...
E: Unable to mount '/system'
It said successful but still no OS installed
sorry the problems just keep coming and coming

First, you can try wiping system and data partitions prior to installing (don't wipe sd card), but I think you need to update your firmware to install sense 6 Roms.
To do that you'll need to s-off first. Revone might work for you and rumrunner should work.
Or you can try installing this sense 5.5 rom. http://forum.xda-developers.com/showthread.php?p=50715903

jollywhitefoot said:
First, you can try wiping system and data partitions prior to installing (don't wipe sd card), but I think you need to update your firmware to install sense 6 Roms.
To do that you'll need to s-off first. Revone might work for you and rumrunner should work.
Or you can try installing this sense 5.5 rom. http://forum.xda-developers.com/showthread.php?p=50715903
Click to expand...
Click to collapse
Thank you for the past 2 days of helping, i have finally fixed it :highfive:

radster12795 said:
Thank you for the past 2 days of helping, i have finally fixed it :highfive:
Click to expand...
Click to collapse
No problem. Did flashing the ROM in post 8 work?

jollywhitefoot said:
No problem. Did flashing the ROM in post 8 work?
Click to expand...
Click to collapse
YES!! it worked perfectly, Thank you very much
thinking about upgrading to sense 6 now