Database Info

very weird CWM/hboot error

Trying to revert to CM9 Alpha 5. Nandroid backup was successful but I got this error as Itried to wipe:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't mount /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't mount /cache/recovery/last_log
Click to expand...
Click to collapse
Trying to do a factory reset via the hboot only boots into recovery. Anyone have any ideas as to what's wrong?

blackknightavalon said:
Trying to revert to CM9 Alpha 5. Nandroid backup was successful but I got this error as Itried to wipe:
Trying to do a factory reset via the hboot only boots into recovery. Anyone have any ideas as to what's wrong?
Click to expand...
Click to collapse
I had this same issue a few days ago when I tried out Virtuous Infinity. CWM 5.0.2.7 was normal until I flashed Infinity.
I'm not sure what did it, but the problem went away after
1. formatting my SD card (since I traded SD cards with my gf),
2. fastboot flashing CWM 5.0.2.7,
3. flashing Blue's wipe utilities (bottom of post), and
4. doing a clean install of CM9 A5.
As I said, I'm not sure what fixed the issue...but one of these 4 things seemed to fix it. Let me know if one of the steps works for you.
....As I finished typing this out, I started getting the intermittent data issue on CM9 A5. It's weird because I haven't had the issue for over a month since I did JuopunutBear S-OFF. I'm in North NJ and noticed you're in NYC. Just curious: have you been getting the intermittent data issue on your device at all?

jjbz said:
I had this same issue a few days ago when I tried out Virtuous Infinity. CWM 5.0.2.7 was normal until I flashed Infinity.
I'm not sure what did it, but the problem went away after
1. formatting my SD card (since I traded SD cards with my gf),
2. fastboot flashing CWM 5.0.2.7,
3. flashing Blue's wipe utilities (bottom of post), and
4. doing a clean install of CM9 A5.
As I said, I'm not sure what fixed the issue...but one of these 4 things seemed to fix it. Let me know if one of the steps works for you.
....As I finished typing this out, I started getting the intermittent data issue on CM9 A5. It's weird because I haven't had the issue for over a month since I did JuopunutBear S-OFF. I'm in North NJ and noticed you're in NYC. Just curious: have you been getting the intermittent data issue on your device at all?
Click to expand...
Click to collapse
I get the intermittent data bug once in a while. Right now I'm flashing the original PG59IMG.zip file and revert back to stock. I think it might be the HTCDev tool corrupting the cache partition.
Sent from Spaceball One.

blackknightavalon said:
Trying to revert to CM9 Alpha 5. Nandroid backup was successful but I got this error as Itried to wipe:
Trying to do a factory reset via the hboot only boots into recovery. Anyone have any ideas as to what's wrong?
Click to expand...
Click to collapse
Have you by any chance used or are using CWM 6?

Oh No. I looked at your signature and you are using it.
These are the first 2 lines of the CWM 6 OP.......
Clockworkmod 6.0.0.0 Alpha Full touch recovery for the myTouch 4G Slide
As of right now, I don't recommend using this recovery until issues are resolved

WeekendsR2Short said:
Oh No. I looked at your signature and you are using it.
These are the first 2 lines of the CWM 6 OP.......
Clockworkmod 6.0.0.0 Alpha Full touch recovery for the myTouch 4G Slide
As of right now, I don't recommend using this recovery until issues are resolved
Click to expand...
Click to collapse
Which explains the cache errors. Just got home from work. I'm flashing the old PG59IMG.zip now.

GOOD LUCK.....but I didn't have any success.

WeekendsR2Short said:
GOOD LUCK.....but I didn't have any success.
Click to expand...
Click to collapse
Just out of curiosity, how long should it take userdata to finish flashing?

blackknightavalon said:
Just out of curiosity, how long should it take userdata to finish flashing?
Click to expand...
Click to collapse
It hanging there is an anomolie. If you press volume + (=YES) it should accept it and move on.

WeekendsR2Short said:
It hanging there is an anomolie. If you press volume + (=YES) it should accept it and move on.
Click to expand...
Click to collapse
have you tried using the other cwm that wildchild post i think it is 5.5

mattlowry said:
have you tried using the other cwm that wildchild post i think it is 5.5
Click to expand...
Click to collapse
I have. It seems just fine and I nor anyone else I've heard about has had one single problem from 5.5.0.4 but to err on the side of safety I've personally gone back to the last official release.....5.0.2.7. I just wish everyone would get into the habit of ALWAYS rereading the OP BEFORE making the assumption that nothing has changed since the original posting. XTC put up the warning against using CWM 6 until issues had been addressed.....if I'm not mistaken....the very same day as the original post.
We have to all remember that no developer nor code is perfect and if we don't have the time to read, read, read and reread a thread then we don't REALLY have the time to be messing around with the heart & souls of our phones. We should be aware that we are doing more than just trying out exciting new things on our phones. We are all educating ourselves.....users & developers alike. And with any education comes certain risks & costs but when it comes down to it the biggest thing we should never do is to just ASS U ME.
IMHO, of course.

This just happened to me too. CWM 6 is bad. It corrupted a backup I had when I was runnng Virtuous Iniquisition.
Go to 5.0.2.7 now. Or else, in the long run like me, your phone will just **** itself and die.

MewTech said:
This just happened to me too. CWM 6 is bad. It corrupted a backup I had when I was runnng Virtuous Iniquisition.
Go to 5.0.2.7 now. Or else, in the long run like me, your phone will just **** itself and die.
Click to expand...
Click to collapse
Too late. It's dead.
This is why I still maintain my G2 as a backup.

If it is less than a year old Tmo will exchange it even without THEIR added on insurance. HTC backs it that long themselves.

can someone please post a PG59IMG.zip with the good CWM recovery? i want to flash the recovery and see if i can manage to get use of my DS again
---------- Post added at 04:35 AM ---------- Previous post was at 04:33 AM ----------
blackknightavalon said:
Too late. It's dead.
This is why I still maintain my G2 as a backup.
Click to expand...
Click to collapse
I wish we had 4EXT recovery on the DS too, i once got this error with the G2 and formatting all but SD through 4EXT fixed the problem.

cybot_x1024 said:
can someone please post a PG59IMG.zip with the good CWM recovery? i want to flash the recovery and see if i can manage to get use of my DS again
---------- Post added at 04:35 AM ---------- Previous post was at 04:33 AM ----------
I wish we had 4EXT recovery on the DS too, i once got this error with the G2 and formatting all but SD through 4EXT fixed the problem.
Click to expand...
Click to collapse
I believe if you will take a look at this info that Blue6IX so kindly put together for us, you'll find the one you're looking for......
http://forum.xda-developers.com/showpost.php?p=17424340&postcount=24
And GOOD LUCK! :good:

[Q] HELP!! Iacidentally wiped my TF300

I accidentally wiped my TF300 and now i cant even get it to go into bootloader, it just goes straight to TWRP. I'm know what i did wrong - causing the wipe- but now i cant get any img to apply to the tab. it will mount system but not cache or anything else. i cant change my recovery because i cant get to bootloader. Any ideas??

LancasterCI said:
I accidentally wiped my TF300 and now i cant even get it to go into bootloader, it just goes straight to TWRP. I'm know what i did wrong - causing the wipe- but now i cant get any img to apply to the tab. it will mount system but not cache or anything else. i cant change my recovery because i cant get to bootloader. Any ideas??
Click to expand...
Click to collapse
Dude... I could be wrong, but enjoy your paperweight.

You might have luck doing this. Go to Asus site and download the full image for your tablet based on SKU region. Extract it to get the blob file. Do you have fastboot setup? Turn off your tablet completely and turn it on my holding the vol down and power it should allow you to boot into fast boot. You can flash the image that way. By
> fastboot -i 0x0B05 flash system C:...\Path-to-blob\blob
> fastboot -i 0x0B05 reboot

LancasterCI said:
I accidentally wiped my TF300 and now i cant even get it to go into bootloader, it just goes straight to TWRP. I'm know what i did wrong - causing the wipe- but now i cant get any img to apply to the tab. it will mount system but not cache or anything else. i cant change my recovery because i cant get to bootloader. Any ideas??
Click to expand...
Click to collapse
If you were on JB download 10.4.2.20, unzip once and place the new zip on your external sdcard. If you were on ICS choose 9.4.3.30 unzip once and place the new zip on your external sdcard.
install zip with twrp.
Good Luck!

hmm
ok just to make sure i am looking for my correct SKU would it be JP or US i beleive the latter since i am in ths US, but i do want to make sure as to to make the problem worse

LancasterCI said:
ok just to make sure i am looking for my correct SKU would it be JP or US i beleive the latter since i am in ths US, but i do want to make sure as to to make the problem worse
Click to expand...
Click to collapse
If you have a US tablet then US.

more issues
So i have the correct Firmware matching SKU, but whe i go to flash i get the following error
E: unable to mount ' /data ' (tw_mount)
E: unable to mount ' /cache ' (tw_mount)
then is repeats but it dose verify the filesystems and partition sizes
Any other ideas. just but this but not sure if bricked is and excuse for a return

LancasterCI said:
So i have the correct Firmware matching SKU, but whe i go to flash i get the following error
E: unable to mount ' /data ' (tw_mount)
E: unable to mount ' /cache ' (tw_mount)
then is repeats but it dose verify the filesystems and partition sizes
Any other ideas. just but this but not sure if bricked is and excuse for a return
Click to expand...
Click to collapse
Were you on 4.2.1 prior to this or encrypted?

LancasterCI said:
So i have the correct Firmware matching SKU, but whe i go to flash i get the following error
E: unable to mount ' /data ' (tw_mount)
E: unable to mount ' /cache ' (tw_mount)
then is repeats but it dose verify the filesystems and partition sizes
Any other ideas. just but this but not sure if bricked is and excuse for a return
Click to expand...
Click to collapse
Don't use clockwork. Extract the zip until you see the blob file. Use fastboot to flash it. It is very easy to do. see my post above. Good luck

defiantj3 said:
Don't use clockwork. Extract the zip until you see the blob file. Use fastboot to flash it. It is very easy to do. see my post above. Good luck
Click to expand...
Click to collapse
OP can't access the bootloader menu so he can't access fastboot.
Thanks for trying.

tobdaryl said:
Were you on 4.2.1 prior to this or encrypted?
Click to expand...
Click to collapse
i did have the latest ota update i believe 4.2.1

LancasterCI said:
i did have the latest ota update i believe 4.2.1
Click to expand...
Click to collapse
I was afraid that was where we were going.
The good, bad, and the ugly.
I'm sorry to tell you that you will probably stuck here until we get the full firmware update from Asus. We are hoping it will drop this week.
I don't know how to help yet on 4.2.1.
Here is a thread you might want to subscribe to where people with your issue are gathering till a resolution is found.
I wish I had better news but the one good thing I can say is there are some devs watching the thread and preparing for the release.
Good Luck!

tobdaryl said:
I was afraid that was where we were going.
The good, bad, and the ugly.
I'm sorry to tell you that you will probably stuck here until we get the full firmware update from Asus. We are hoping it will drop this week.
I don't know how to help yet on 4.2.1.
Here is a thread you might want to subscribe to where people with your issue are gathering till a resolution is found.
I wish I had better news but the one good thing I can say is there are some devs watching the thread and preparing for the release.
Good Luck!
Click to expand...
Click to collapse
Well any idea exactly what happened or if it is even fixable??

LancasterCI said:
Well any idea exactly what happened or if it is even fixable??
Click to expand...
Click to collapse
We think it has to do with encryption of your tablet when updating to 4.2.1 and the effects are not removed by downgrading.
update-binary also changed with 4.2.1 and we are looking into the changes as they need to be known to create zips for flashing. Other changes as well.
4.2.1 appears to encrypt by default; I think it is done to enable multi-user to restrict access to any other account.
Sorry I forgot fixable. Yes I believe once the update drops it will be resolved. That is why I provided the link.

tobdaryl said:
We think it has to do with encryption of your tablet when updating to 4.2.1 and the effects are not removed by downgrading.
update-binary also changed with 4.2.1 and we are looking into the changes as they need to be known to create zips for flashing. Other changes as well.
4.2.1 appears to encrypt by default; I think it is done to enable multi-user to restrict access to any other account.
Sorry I forgot fixable. Yes I believe once the update drops it will be resolved. That is why I provided the link.
Click to expand...
Click to collapse
Thanks to all for the help will continue to chck back.. Thank god for my nexus 7

LancasterCI said:
Thanks to all for the help will continue to chck back.. Thank god for my nexus 7
Click to expand...
Click to collapse
I'm sorry.
Good Luck!

Hi LancasterCI,
After several test with the new ota update I have also had similar issue with recovery no being able to mount anything but system.
However my fastboot was still working so we need to get that up and running first.
What I believe is happening is that the new bootloader is not actually encrypting anything but rather reformatting the cache, data partitions to a format that twrp & cwm are not looking for.
pjc21; said:
After reading through some of the posts in the twrp thread with similar issues. I seems that twrp looks for these partitions (data, system, cache, etc) to be in a certain format, ie ext4. However is the ext twrp is looking for does not exist (say the ext4 is now ext3) twrp will assume that it is encrypted and will bring up a password prompt and be unable to mount.
So with the test I have done to confirm that flashing just the new 4.2.1 bootloader and nothing else wiil encrypt the custom recoveries, could it be that the new 4.2.1 bootloader is reformatting these partitions to some other format making twrp & cwm assume that these partitions are now encrypted??
Click to expand...
Click to collapse
What we need to do 1st is get fastboot working for you, now I think we can get adb working by following this how-to just follow on from the device manager part to get adb working in recovery provided you have adb setup on your pc already.
Once you have adb working try the following command to reboot into bootloader, sometimes the tab just needs a hard reboot.
Code:
adb reboot bootloader
If this works, boot into fastboot and follow my post here, once done you'll be back on stock 4.1.1 but will then be able to boot back into fastboot and flash custom recovery and custom rom again.
Hope this helps.

pjc21 said:
Hi LancasterCI,
After several test with the new ota update I have also had similar issue with recovery no being able to mount anything but system.
However my fastboot was still working so we need to get that up and running first.
What I believe is happening is that the new bootloader is not actually encrypting anything but rather reformatting the cache, data partitions to a format that twrp & cwm are not looking for.
What we need to do 1st is get fastboot working for you, now I think we can get adb working by following this how-to just follow on from the device manager part to get adb working in recovery provided you have adb setup on your pc already.
Once you have adb working try the following command to reboot into bootloader, sometimes the tab just needs a hard reboot.
Code:
adb reboot bootloader
If this works, boot into fastboot and follow my post here, once done you'll be back on stock 4.1.1 but will then be able to boot back into fastboot and flash custom recovery and custom rom again.
Hope this helps.
Click to expand...
Click to collapse
ok I got back into the boot loader but i cant flash anyhting it wont even let me change my recovery
I get this message
"erroe: cannot load 'stock.blob' : No error"

The 4.2.1 update is on Asus so with luck we will start to see resolutions for these problems

Found the ultimate recovery, the receipt!!! The retailer exchanged it no questions asked. I know it the noon way out but now I have a fresh slate to start with and won't be flashing 4.2 anytime soon. I do however want to thank you all for your support and help. I'm definitely gonna be modding my tab as soon as the devs get a good fix going. BTW would love to for and a toolkit for this eventually, please devs??
Sent from my Nexus 7 using xda app-developers app

[Q] No OS Installed, Can't Mount /data [Solved]

Okayyyy.... So, I was a bit foolish and when trying to install CM11, I wiped my internal storage. So now I don't have OS on my phone. Also, I cannot mount /data in TWRP 2.6.3.0. What to do next as there is no RUU available for Mini? ADB Sideload doesn't work either due to me not being able to mount /data. What do do now? :I

you wiped your internal-SD and have no ROM.zip to install anything? happened to me a few days ago
you can install a ROM via ADB (never did this) or push a new ROM.zip on your /sdcard/ via "adb push" and install this within recovery.

theodorius123 said:
you wiped your internal-SD and have no ROM.zip to install anything? happened to me a few days ago
you can install a ROM via ADB (never did this) or push a new ROM.zip on your /sdcard/ via "adb push" and install this within recovery.
Click to expand...
Click to collapse
Okay, I was able to push the CM & gapps zips into my sdcard, but I still cannot mount /data, so I am unable to install it :/ Any more suggestions?
Edit: seems that TWRP also says "unable to mount internal storage".

Okay, I got it solved Had to flash stock recovery, do factory reset and then re-flash TWRP, and I was able to mount /data and internal storage again

Aciz said:
Okay, I got it solved Had to flash stock recovery, do factory reset and then re-flash TWRP, and I was able to mount /data and internal storage again
Click to expand...
Click to collapse
Still haven't been able to find the stock recovery for a HTC One Mini INTL, can anybody link me? I've searched XDA and google everywhere.

Aciz said:
Okay, I got it solved Had to flash stock recovery, do factory reset and then re-flash TWRP, and I was able to mount /data and internal storage again
Click to expand...
Click to collapse
Tell me please where did you find the mini(m4) stock recovery, 'cause yes there are no RUU's out there for the mini and I literally got the same problem as yours I wiped the internal storage no OS, etc. and unable to mount data. I'm hopeless tried everything..I pushed the zip to data/media and it successfully copied but as you know unable to mount data so no use. Please tell me where can I get the stock recovery img file.
Thank you in advance.

l3raveHeart said:
Tell me please where did you find the mini(m4) stock recovery, 'cause yes there are no RUU's out there for the mini and I literally got the same problem as yours I wiped the internal storage no OS, etc. and unable to mount data. I'm hopeless tried everything..I pushed the zip to data/media and it successfully copied but as you know unable to mount data so no use. Please tell me where can I get the stock recovery img file. :crying:
Thank you in advance.
Click to expand...
Click to collapse
I can't remember where I got it I'm afraid, but I might still have it on my PC. But I won't be home until Sunday evening

Aciz said:
I can't remember where I got it I'm afraid, but I might still have it on my PC. But I won't be home until Sunday evening
Click to expand...
Click to collapse
Thanks for your reply really appreciate it... don't have to worry about it no more I've found it and my phone is now back to life, but I have to admit it without your post I would have been still searching for a solution.
Thanks again. :good: :highfive:

l3raveHeart said:
Thanks for your reply really appreciate it... don't have to worry about it no more I've found it and my phone is now back to life, but I have to admit it without your post I would have been still searching for a solution.
Thanks again. :good: :highfive:
Click to expand...
Click to collapse
Can you please post the stock recovery. I did something similar and can't manage to get a rom back on to my phone.
I currently have OS-3.10.502.3.
Thanks

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

[Q] HELP! TWRP cannot mount data or detect sdcard... what to do?

Just for clarification, I am a newb and my TF300T is running 4.2.1 JB, running the 10.6.1.27.5 build. For some odd reason, everything was successful during rooting and unlocking the device, however it fails to mount the data and sdcard and doesn't even recognise that there is anything on either. It wouldn't even recognize that an external sd card can be mounted. I flashed TWRP on after flashing CWM using http://forum.xda-developers.com/show....php?t=2041627 which was designed for 4.1.x (I didn't know at the time that using this method was potentially dangerous for the device at the time) but both are displaying the same problem. Does anyone know what I can do? Any help would greatly appreciated!
[This is a repost as I put it on Q&A subsection but realised it might be better if I posted it here]

naturesenshi said:
Just for clarification, I am a newb and my TF300T is running 4.2.1 JB, running the 10.6.1.27.5 build. For some odd reason, everything was successful during rooting and unlocking the device, however it fails to mount the data and sdcard and doesn't even recognise that there is anything on either. It wouldn't even recognize that an external sd card can be mounted. I flashed TWRP on after flashing CWM using http://forum.xda-developers.com/show....php?t=2041627 which was designed for 4.1.x (I didn't know at the time that using this method was potentially dangerous for the device at the time) but both are displaying the same problem. Does anyone know what I can do? Any help would greatly appreciated!
[This is a repost as I put it on Q&A subsection but realised it might be better if I posted it here]
Click to expand...
Click to collapse
What version of twrp are you running ?
Thx Josh

lj50036 said:
What version of twrp are you running ?
Thx Josh
Click to expand...
Click to collapse
I initially installed 2.2.0 then installed 2.8.5 after realising my mistake (I made a lot of mistakes...) Thanks for the reply!

naturesenshi said:
I initially installed 2.2.0 then installed 2.8.5 after realising my mistake (I made a lot of mistakes...) Thanks for the reply!
Click to expand...
Click to collapse
and 2.8.5.0 will not mount /data either ?
Thx Josh

lj50036 said:
and 2.8.5.0 will not mount /data either ?
Thx Josh
Click to expand...
Click to collapse
Nope, won't mount anything at all. I could send you a picture of the manifest in the morning, if you'd like? I remember that being where i saw it produce error codes like E:\ failed to mount data or something like that

naturesenshi said:
Nope, won't mount anything at all. I could send you a picture of the manifest in the morning, if you'd like? I remember that being where i saw it produce error codes like E:\ failed to mount data or something like that
Click to expand...
Click to collapse
Ok well as long as you dont have anything that needs saved .....
Go into twrp go to wipe, format, type yes ....
This can take up to 90 mins so plug it into power ......
Do not interrupt this process ....
Once finished reboot back into recovery and make sure /data can be mounted .....
Just know TWRP will ask to install SU say 'NO' and also it will give you a warning about no OS installed ....
This is ok as there is no system to install SU on and there is no OS cause you formatted ....
Then you can use adb or mtp to move a rom on the tab and flash .....
Thx Josh

lj50036 said:
Ok well as long as you dont have anything that needs saved .....
Go into twrp go to wipe, format, type yes ....
This can take up to 90 mins so plug it into power ......
Do not interrupt this process ....
Once finished reboot back into recovery and make sure /data can be mounted .....
Just know TWRP will ask to install SU say 'NO' and also it will give you a warning about no OS installed ....
This is ok as there is no system to install SU on and there is no OS cause you formatted ....
Then you can use adb or mtp to move a rom on the tab and flash .....
Thx Josh
Click to expand...
Click to collapse
Before reading this I tried to go get a picture, but lo and behold, it was actually working ! So I flashed Katkiss' 5.1 rom which worked like a charm. Don't know what caused it to start working suddenly, but I won't complain! Thank you so much for the help!