Database Info

[SOLVED] Soft Brick... Can't install ROMS and pushing does not work.

First of all I decided to install CM10 without making a backup on TWRP 2 (clever Kyle). Then when it was stuck on the bootanimation for about an hour, I got annoyed and looked through the forums for help. "Factory reset, clear caches before installing etc" So I deleted the ROM, factory reset via TWRP, deleted both cache and then tried to install CM10. Failed.
Then I tried to mount the SD card to my computer to try to find other ROMS to install. Viper and Energy both failed. I then tried CM10, Viper and Energy with CWM 5.8, and the installation of all gets aborted almost instantly, which I am guessing means that it failed on there as well. I then tried ADB, and pushing keeps failing. Does anybody have any ideas at all on how to get just any ROM onto the phone so that I can get the official 4.1 update again (my phone was on 4.1 before trying CM10, so the HBOOT is most likely 4.1 as well). Any advice would be greatly appreciated, because having a £350 paperweight is not what I particularly want, especially considering I have another 9 months contract to run and no spare phone on the same network as my current contract.

kylepont said:
Any advice would be greatly appreciated
Click to expand...
Click to collapse
When you say that installing ROMs fails and adb pushing fails, you should tell us what error messages you get.
If you can still get into bootloader, you're probably going to be fine.
First, check that you can mount your sdcard in recovery. I don't mean mount onto your PC over USB, but just mount the sdcard partition onto the root filesystem.
If you can not get into recovery, re-flash one.
If recovery can not mount the sdcard, then you have to go to the sticky on how to fix unmountable sdcard. It involves flashing a stock recovery and then clearing storage from bootloader.
If your recovery is good and your sdcard is mountable, adb pushing should work. If it doesn't, post error messages. Make sure your sdcard is mounted before you try to push fils to it.
In recovery, format system, data, cache, but not sdcard. Then flash a zip. Then boot back into bootloader/fastboot and fastboot flash the boot image that comes with the rom. (Did you do this last step when flashing other roms?)
If this does not work not for you, describe in detail what you do and what you see. If it does work out, I suggest you make a nandroid backup so you can get back to this state, and S-off the device.
-Jobo

touch of jobo said:
If this does not work not for you, describe in detail what you do and what you see.
Click to expand...
Click to collapse
Sometimes a print screen can speak louder than words. This is the problem, I followed the tutorial posted specifically for my phone and that didn't work. (I used a dropbox link because I could only upload 640 x 640 according to the attachments screen, so you can see the full picture here)
www(dot)dropbox(dot)com/s/ei0y16oar828dh4/Picture1(dot)png
EDIT: I used platform-tools instead of tools because Google decided to move the adb application to that folder in the most recent update

Re: [Q] Soft Brick... Can't install ROMS and pushing does not work.
kylepont said:
Sometimes a print screen can speak louder than words. This is the problem, I followed the tutorial posted specifically for my phone and that didn't work. (I used a dropbox link because I could only upload 640 x 640 according to the attachments screen, so you can see the full picture here)
www(dot)dropbox(dot)com/s/ei0y16oar828dh4/Picture1(dot)png
EDIT: I used platform-tools instead of tools because Google decided to move the adb application to that folder in the most recent update
Click to expand...
Click to collapse
Have you flashed the boot.img?
fastboot flash boot boot.img
Sent from my One S using Tapatalk 2

usaff22 said:
Have you flashed the boot.img?
fastboot flash boot boot.img
Click to expand...
Click to collapse
boot.img? (Noob question incoming, prepare your anuses) What is a boot.img and why do I need it?

kylepont said:
Sometimes a print screen can speak louder than words.
Click to expand...
Click to collapse
You get this:
cannot stat 'ROM.zip': No such file or directory
..because either you have not mounted your /sdcard partition, but more likely because you dont have ROM.zip in your working directory.
Either move ROM.zip to the same directory where adb sits, or use:
adb push C:\full\path\to\rom.zip /sdcard/
Also, is the file youre trying to push actually named 'ROM.zip' or something else, like ViperOneS_2.1.0.zip or so..
Edit:
kylepont said:
boot.img? (Noob question incoming, prepare your anuses) What is a boot.img and why do I need it?
Click to expand...
Click to collapse
The flashing instructions for your ROM will likely state that you have to 'flash the boot image (or boot.img or kernel) in fastboot before booting into the rom.
You can find a file named 'boot.img' inside your rom zip. You have to flash that in fastboot. You can do it before or after flashing the rom, but you must do it before booting into the rom.

kylepont said:
usaff22 said:
Have you flashed the boot.img?
fastboot flash boot boot.img/QUOTE]
boot.img? (Noob question incoming, prepare your anuses) What is a boot.img and why do I need it?
Click to expand...
Click to collapse
Extract the boot.img file from the ROM. Place it in your adb folder. Boot into bootloader, select fastboot and connect to PC. Type command fastboot flash boot boot img
Click to expand...
Click to collapse

touch of jobo said:
You get this:
cannot stat 'ROM.zip': No such file or directory
..because either you have not mounted your /sdcard partition, but more likely because you dont have ROM.zip in your working directory.
Either move ROM.zip to the same directory where adb sits, or use:
adb push C:\full\path\to\rom.zip /sdcard/
Also, is the file youre trying to push actually named 'ROM.zip' or something else, like ViperOneS_2.1.0.zip or so..
Click to expand...
Click to collapse
All the boxes are ticked on the TWRP Mount screen, including System and SD card. And yes, I did make sure that it is:
1) in the same folder as the adb
2) called ROM.zip. I tried re-naming it CM10.zip and tried that in the adb and still no luck, without without the .zip file suffix.
And usaff22, does that involve unzipping the ROM that I am using?

Okay, so the boot.img was flashed successfully. I then went back onto TWRP, tried to flash the zip and it failed...

kylepont said:
I did make sure that it is [...] called ROM.zip. I tried re-naming it CM10.zip and tried that in the adb and still no luck, without without the .zip file suffix.
Click to expand...
Click to collapse
It can not find the local file. Make sure the file is not actually called 'ROM.zip.zip' (with 2x .zip ... you seem to have extensions hidden for most types but it shows .zip).
kylepont said:
Okay, so the boot.img was flashed successfully. I then went back onto TWRP, tried to flash the zip and it failed...
Click to expand...
Click to collapse
Which version of TWRP? I don't use it, but I read that the latest version has issues and you should use the previous version (2.2.0? I dont know).
Also, does it say anything interesting when it fails?
Before flashing the zip, did you format your system, data, cache partitions?

EDIT: After repeatedly trying to adb push, I finally got CM10.zip.zip onto the phone. Flashing took a bit longer than last time, but booting took no time at all. Thank you touch of jobo and usaff22, your advice was a lot of help.
touch of jobo said:
It can not find the local file. Make sure the file is not actually called 'ROM.zip.zip' (with 2x .zip ... you seem to have extensions hidden for most types but it shows .zip).
Click to expand...
Click to collapse
Ah, putting .zip.zip fixed that error, but has now given me a new one: protocol failure
touch of jobo said:
Which version of TWRP? I don't use it, but I read that the latest version has issues and you should use the previous version (2.2.0? I dont know).
Click to expand...
Click to collapse
TWRP v.2.3.3.0. Do you recommend an older build then, or do you think that CWM is a better tool for the job? (I have that on standby)
touch of jobo said:
Before flashing the zip, did you format your system, data, cache partitions?
Click to expand...
Click to collapse
I haven't done that again... Should I do that again? All that is on the system is the boot.img and the CM10.zip folder

kylepont said:
Ah, putting .zip.zip fixed that error, but has now given me a new one: protocol failure
Click to expand...
Click to collapse
I can't help with that adb error. Never seen it. Try searching the forums for it. Sorry. Also, I don't use Windows, so I don't know about driver versions and things.
kylepont said:
TWRP v.2.3.3.0. Do you recommend an older build then, or do you think that CWM is a better tool for the job? (I have that on standby)
Click to expand...
Click to collapse
TWRP and CWM are both fine for flashing ROMs, just not this specific version of TWRP. Since I dont use it myself, I dont know the exact version numbers, but read around a bit and you'll find what worked for others.
Maybe flashing a different recovery will even get rid of your protocol error.
If you've made nandroid backups (I guess you havent or we wouldnt be here.. sorry) you should stay with the same recovery (same 'brand', not same version) or you can't restore them.
kylepont said:
I haven't done that again... Should I do that again? All that is on the system is the boot.img and the CM10.zip folder
Click to expand...
Click to collapse
The CM10.zip should be on your sdcard, not your system partition. You dont need the boot img at all on your device. You need it on your PC in order to fastboot flash it.
Before flashing a ROM you should wipe your 'system', 'data', and 'cache' partitions, but not your 'sdcard' partition. Only if you flash (a newer version of) the same ROM you have operational, then you can sometimes flash without wiping. This is called 'dirty flashing'. But this does not apply in your case.

Successful flash of CyanogenMod, thanks for the help.
I would like to thank touch of jobo and usaff22 for their help, I just hope that somebody else will see this thread and get all of the answers that they need.

Re: [Q] Soft Brick... Can't install ROMS and pushing does not work.
kylepont said:
I would like to thank touch of jobo and usaff22 for their help, I just hope that somebody else will see this thread and get all of the answers that they need.
Click to expand...
Click to collapse
I would rename the zip to something else like sense.zip, place it on the desktop and do adb push C:\Users\username\Desktop\sense.zip /sdcard/
Make sure you use backward slashes for the PC file location, and forward slashes for the phone paste location.
This way we are also providing the full path on the PC.
Also make sure you use the latest adb from the SDK website. You don't need the whole thing, just the platform-tools bit, and replace the files in the new folder with the old one.
Sent from my One S using Tapatalk 2

Oh, while you're here, another problem has come about. Mounting the SD card will not work, and I can't replace it with a new SD card because... Well, there is no removable cover. I know how to fix it, I've read enough on here to find that out, but the only thing that I am missing is a stock recovery image for the S4 version (CID is ORANG001 if that is required) so if anybody knows a link for this then that will be greatly appreciated.

kylepont said:
Oh, while you're here, another problem has come about. Mounting the SD card will not work, and I can't replace it with a new SD card because... Well, there is no removable cover. I know how to fix it, I've read enough on here to find that out, but the only thing that I am missing is a stock recovery image for the S4 version (CID is ORANG001 if that is required) so if anybody knows a link for this then that will be greatly appreciated.
Click to expand...
Click to collapse
You might be able to find an RUU lying around on one of the websites which give RUUs such as androidfiles.org/ruu
I tried looking, but no sign of an orange RUU. An easy way to overcome this would be to change your CID to HTC__001 and use an unbranded RUU.

kylepont said:
the only thing that I am missing is a stock recovery image for the S4 version (CID is ORANG001 if that is required)
Click to expand...
Click to collapse
You can extract the recovery image from any RUU or OTA. Recoveries do not depend on carrier.
But .. if you can see your sdcard from within recovery (when 'choosing' a zip to flash, or from an adb shell or so) and from within Android, then you do not have The Unmountable Sdcard Issue and you should not go through that process. Only if you get an 'Unable to mount /sdcard' error in recovery.

touch of jobo said:
If you can see your sdcard from within recovery (when 'choosing' a zip to flash, or from an adb shell or so) and from within Android, then you do not have The Unmountable Sdcard Issue and you should not go through that process. Only if you get an 'Unable to mount /sdcard' error in recovery.
Click to expand...
Click to collapse
So I just use the stock recovery of any RUU I can find lying around for the HTC One S?
usaff22 said:
I tried looking, but no sign of an orange RUU. An easy way to overcome this would be to change your CID to HTC__001 and use an unbranded RUU.
Click to expand...
Click to collapse
How do I change the CID? Because knowing me, I'll screw it up and brick it if that is possible.

kylepont said:
So I just use the stock recovery of any RUU I can find lying around for the HTC One S?
Click to expand...
Click to collapse
Yes. You can use the recovery image from any RUU or OTA.
But first make sure you need it. The stock recovery thing is only to fix the situation where your sdcard is unmountable and you get that error in recovery.
kylepont said:
How do I change the CID? Because knowing me, I'll screw it up and brick it if that is possible.
Click to expand...
Click to collapse
This is the thread: http://forum.xda-developers.com/showthread.php?t=1671643
It involves extracting, hex-editing, and flashing a critical part of your device. If you make the slightest mistake you have a brick. However, if you read carefully and double check every step, it's not difficult. Many have done it. Read the thread.
Once you have supercid, you may as well get s-off as well. (This is the thread: http://forum.xda-developers.com/showthread.php?t=2155135 ) That way you can always flash anything.
Whatever you decide to do, before you start on anything, read all the instructions to the end, so that you're sure you can complete the process before you start. Also, before you start any process, try to understand what each step does and why it is necessary. That may involve a lot of reading and searching, but that is a Good Thing in the end.

touch of jobo said:
Yes. You can use the recovery image from any RUU or OTA.
But first make sure you need it. The stock recovery thing is only to fix the situation where your sdcard is unmountable and you get that error in recovery.
Click to expand...
Click to collapse
It is unmountable. I tried CWM and TWRP to no avail. Also, I have HBOOT version 2.15 which I heard is a bugger to work with. Also, I got the ZIP file for the stock 4.1, and I read that the stock recovery is in the firmware folder, but I cannot access it. (https://www.dropbox.com/s/kyn9sb5x7gpd7fr/Picture2.png) Then, I tried to get to the CID, following the instructions that you gave me, and I didn't get very far (https://www.dropbox.com/s/g6ik0i3los7unde/Picture3.png)

[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

Deleted /system, help!

Hi guys,
My cousin from America came to visit yesterday, and he asked me if I could install CyanogenMod on his phone. It's an HTC One X from AT&T. So I set his CID to 111111, unlocked his bootloader with HTCDev, flashed TWRP 2.5.0.0 and then I rooted his phone. Afterwords, I did a backup via TWRP Recovery.
I looked for the CyanogenMod for this device and the stable build was cm-10.0.0-evita. I transfered it to the phone's TWRP folder, booted recovery and tried to install it but failed, the error message was: assert failed: getprop("ro.bootloader") == 2.1....and some more numbers and stuff
Stupid as I was, I thought "It's probably the stock ROM interfering with the installation, and I can always restore my backup" so I erased a couple of things from the phone: Dalvik Cache, Cache, Data, sdcard and System. Left Android Secure alone because I didn't know what it was or what it does.
Then it hit me. I formatted Data, my backup was gone! And so was the ROM I wanted to flash!
What do I do now? I don't have any operating system installed and can't boot into android! All I can do is boot into Recovery and Bootloader.
Here's what bootloader says:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.09.000
RADIO-0.16.32.09.01_3
OpenDSP-v25.1.0.32.0405
eMMC-boot
Apr 2 2012, 21:08:24
My recovery is: TWRP 2.5.0.0
Any ideas?

It's ok, no need to panic
Download ROM to PC. Make doubly sure it's for this device, I think the error you experienced the first time was because you tried to flash an International One X ROM. Only get your ROMs from here, or here.
Boot into recovery.
Connect the phone to the PC.
Mount your sd/internal storage from your TWRP menu.
Copy ROM from PC to phone.
Wipe cache/dalvik/factory reset/system.
Flash ROM.
Reboot.
Enjoy.
Sent from my Evita

Alright, no problem, the error you got in TWRP was because you needed to have HBOOT 2.14 or above to install CM10.1 because of the kernel it uses. Never wipe /sdcard because it won't do you any good. Now, what you're gonna wanna do is, mount USB Storage in TWRP (under mount menu) when it's connected to your PC, download a ROM (not CM10.1 for now, we'll get to that soon enough) and make sure it's for this phone, drag and drop it to your phone from the PC, and flash it. Once you do that, if you still want to get CM10.1, we can help you with that too.
Edit: @timmaaa he won't be able to use CM10.1 because he's on hboot 1.09.

Your main problem, is that you are deleting/formatting things without having any clue what they are. This is an invitation for disaster. Your backups are deleted because your deleted the SD card, not because you deleted /data or /system.
/system = current ROM
/data = user data (phone storage), formatting is the same as factory reset
The only things that really need to be deleted when flashing a new ROM is /data (factory reset) and cache. Formatting /system is not necessary, as flashing a new ROM does this by default before installing the new ROM.
Connect the phone to your computer, mount USB in TWRP, and move the new ROM zip to the SD card, and flash from TWRP.
Its also a good idea to copy a backup to your computer or Dropbox. But that is probably not something that will help you at the moment. Just a bit of advice moving forward.

While in twrp, plug into your pc then go to mounts > mount usb storage. Then put whatever Rom on there. Make sure you get the right Rom for this device.
EDIT:
Oh wow just realized I was beat by like 3 people before I hit post lol
Sent from my HTC One X using xda premium

dragancla said:
Hi guys,
My cousin from America came to visit yesterday, and he asked me if I could install CyanogenMod on his phone. It's an HTC One X from AT&T. So I set his CID to 111111, unlocked his bootloader with HTCDev, flashed TWRP 2.5.0.0 and then I rooted his phone. Afterwords, I did a backup via TWRP Recovery.
I looked for the CyanogenMod for this device and the stable build was cm-10.0.0-evita. I transfered it to the phone's TWRP folder, booted recovery and tried to install it but failed, the error message was: assert failed: getprop("ro.bootloader") == 2.1....and some more numbers and stuff
Stupid as I was, I thought "It's probably the stock ROM interfering with the installation, and I can always restore my backup" so I erased a couple of things from the phone: Dalvik Cache, Cache, Data, sdcard and System. Left Android Secure alone because I didn't know what it was or what it does.
Then it hit me. I formatted Data, my backup was gone! And so was the ROM I wanted to flash!
What do I do now? I don't have any operating system installed and can't boot into android! All I can do is boot into Recovery and Bootloader.
Here's what bootloader says:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.09.000
RADIO-0.16.32.09.01_3
OpenDSP-v25.1.0.32.0405
eMMC-boot
Apr 2 2012, 21:08:24
My recovery is: TWRP 2.5.0.0
Any ideas?
Click to expand...
Click to collapse
First off flash twrp 2.3.3.1 or 2.6 all others have issues.
Then mount usb storage from twrp
Copy Rom to sd card
Wipe cache and dalvik
If you're not s-off depending on hboot version the boot image will need to be flashed via fastboot.
Boot into rom.
Good luck.
Edit: just saw your on 1.09 no need to flash boot image first.
Sent from my HTC One XL using xda premium

Oh by the way, TWRP 2.5 is known to have issues, so try using TWRP 2.3.3.1 instead.
You'll need to change recovery versions before doing any of the steps I mentioned above.
Sent from my Evita

timmaaa said:
Oh by the way, TWRP 2.5 is known to have issues, so try using TWRP 2.3.3.1 instead.
You'll need to change recovery versions before doing any of the steps I mentioned above.
Click to expand...
Click to collapse
TWRP 2.6 has been recently released, and appears to have resolved the issues with 2.5. But yeah, 2.5 and 2.4 are known to cause some serious problems (many ROMs will fail to flash).

Lol. All together now.
Sent from my Evita
---------- Post added at 12:37 AM ---------- Previous post was at 12:31 AM ----------
redpoint73 said:
TWRP 2.6 has been recently released, and appears to have resolved the issues with 2.5. But yeah, 2.5 and 2.4 are known to cause some serious problems (many ROMs will fail to flash).
Click to expand...
Click to collapse
Yeah I've heard it's working well, I'm gonna give it a spin hopefully in the next few days. I just thought it'd be best to suggest something we know for sure is solid for right now.
Sent from my Evita

Wow, thanks for the quick responses!
First of all, I can't mount SD card from TWRP. I can mount cache, data and System, but the checkbox nextto sdcard can't be clicked, stays unchecked. I can mount USB Storage but my computer says it needs to format the drive to use it, and I'm using Windows not Linux.
Secondly, whenever i try to flash openrecovery-twrp-2.3.1.0-evita.img with adb fastboot it says "The filename, directory name, or volume syntax is incorrect".
What do I do? :S

Also, after I've done this, what ROM do you suggest I download to flash, given my bootloader and situation?

dragancla said:
Wow, thanks for the quick responses!
First of all, I can't mount SD card from TWRP. I can mount cache, data and System, but the checkbox nextto sdcard can't be clicked, stays unchecked. I can mount USB Storage but my computer says it needs to format the drive to use it, and I'm using Windows not Linux.
Secondly, whenever i try to flash openrecovery-twrp-2.3.1.0-evita.img with adb fastboot it says "The filename, directory name, or volume syntax is incorrect".
What do I do? :S
Click to expand...
Click to collapse
You must have done a factory reset from bootloader, which has corrupted your storage. So, mount usb storage then format it using Windows to fat32 format.
The error you're encountering while trying to flash recovery is most likely because you're giving adb incorrect or mistyped command. To make it easier on yourself, rename the recovery zip file on your pc to something simple like "twrp.img" then issue the following command exactly:
fastboot flash recovery twrp.img
Sent from my Evita

dragancla said:
First of all, I can't mount SD card from TWRP. I can mount cache, data and System, but the checkbox nextto sdcard can't be clicked, stays unchecked.
Click to expand...
Click to collapse
You didn't do a factory reset from bootloader did you?

RollTribe said:
You didn't do a factory reset from bootloader did you?
Click to expand...
Click to collapse
Looks like he did. Instructions given above.
Sent from my Evita
---------- Post added at 12:53 AM ---------- Previous post was at 12:52 AM ----------
dragancla said:
Also, after I've done this, what ROM do you suggest I download to flash, given my bootloader and situation?
Click to expand...
Click to collapse
You can flash pretty much any Sense ROM, and most aosp ROMs (just not the ones with the 3.4 kernel).
Sent from my Evita

RollTribe said:
You didn't do a factory reset from bootloader did you?
Click to expand...
Click to collapse
I did :S Thought it would help...
timmaaa said:
You must have done a factory reset from bootloader, which has corrupted your storage. So, mount usb storage then format it using Windows to fat32 format.
The error you're encountering while trying to flash recovery is most likely because you're giving adb incorrect or mistyped command. To make it easier on yourself, rename the recovery zip file on your pc to something simple like "twrp.img" then issue the following command exactly:
fastboot flash recovery twrp.img
Sent from my Evita
Click to expand...
Click to collapse
Thanks, it worked! I can mount sdcard now!
What's the next step?

dragancla said:
I did :S Thought it would help...
Yeah, never do that...
Thanks, it worked! I can mount sdcard now!
What's the next step?
Click to expand...
Click to collapse
Now you can flash any ROM you want as long as it isn't AOSP with 3.4 kernel. Unless you really want the 3.4 ROM, but then you'd first have to s-off and then run the RUU to 3.18.

The next step after what? What exactly have you achieved so far?
Sent from my Evita

RollTribe said:
Now you can flash any ROM you want as long as it isn't AOSP with 3.4 kernel. Unless you really want the 3.4 ROM, but then you'd first have to s-off and then run the RUU to 3.18.
Click to expand...
Click to collapse
Would this work? http://forum.xda-developers.com/showthread.php?t=2230754
Or can you link me any ROM that would work for me, please?

dragancla said:
Would this work? http://forum.xda-developers.com/showthread.php?t=2230754
Or can you link me any ROM that would work for me, please?
Click to expand...
Click to collapse
Yeah, that would work. It's a little outdated, but it should work just fine.

timmaaa said:
The next step after what? What exactly have you achieved so far?
Sent from my Evita
Click to expand...
Click to collapse
Well, I can now access the sdcard/internal storage on my PC when I connect the cable in TWRP Recovery. I just need a ROM.

Problems with downgrading to KitKat

Hey guys, I'm trying to downgrade to KitKat after all the issues Lollipop is giving me and the incompatible apps I'm trying to run.
I am following instructions here but I came across a problem when flashing the system.img file.
The error it gives me is:
FAILED (remote: Insufficient memory.)
I can't flash over system and can not boot.
What am I missing? I was rooted and my bootloader unlocked prior to starting and I tried with the factory recovery and the 1.2.1 recovery image.
Edit: My issue has been solved. Flashing the Full OTA.zip file will install KitKat over Lollipop. No need to manually flash each file through fastboot. I wish guides would tell you that instead.

BlackDave said:
Hey guys, I'm trying to downgrade to KitKat after all the issues Lollipop is giving me and the incompatible apps I'm trying to run.
I am following instructions here but I came across a problem when flashing the system.img file.
The error it gives me is:
FAILED (remote: Insufficient memory.)
I can't flash over system and can not boot.
What am I missing? I was rooted and my bootloader unlocked prior to starting and I tried with the factory recovery and the 1.2.1 recovery image.
Click to expand...
Click to collapse
I don't know why that wouldn't work. Have you tried just downloading the image from nvidia HERE?
I'm assuming wifi since your sig says 16GB

Keithn said:
I don't know why that wouldn't work. Have you tried just downloading the image from nvidia HERE?
I'm assuming wifi since your sig says 16GB
Click to expand...
Click to collapse
Those are the same files as the ones I downloaded in the other thread.

I got my tablet working again on Lollipop 5.0.1 but that's not where I want to be. I've searched about my error message but most threads I found went unanswered.

Your best bet might just be to try getting a full OTA and flashing it through cwm or something. I'll try with mine when I have some time to backup and flash, probably later tomorrow. If I find anything out I'll post.
Sent from my SHIELD Tablet

BlackDave said:
I got my tablet working again on Lollipop 5.0.1 but that's not where I want to be. I've searched about my error message but most threads I found went unanswered.
Click to expand...
Click to collapse
I just flashed the images and booted.
Did you accidentally try flashing to the wrong place, such as flashing to boot( which would be too small) instead of system? Did you do all of the commands yourself or use the .bat? My shield disconnected after doing the boot.img and system.img for some reason, so I had to select fastboot protocol to reboot the bootloader and continue to flash the userdata.img, blob, and battery.dtb.

was your tablet internal memory full?, try wipping data and chace and you could use the script that the original Nvidia recovery image has zipped. I went up and down like 3 times, im in kitkat right now and not experiencing any problem.

Iams1002 said:
was your tablet internal memory full?, try wipping data and chace and you could use the script that the original Nvidia recovery image has zipped. I went up and down like 3 times, im in kitkat right now and not experiencing any problem.
Click to expand...
Click to collapse
No I wipped internal data since I keep everything on external and it still didn't work.
Keithn said:
I just flashed the images and booted.
Did you accidentally try flashing to the wrong place, such as flashing to boot( which would be too small) instead of system? Did you do all of the commands yourself or use the .bat? My shield disconnected after doing the boot.img and system.img for some reason, so I had to select fastboot protocol to reboot the bootloader and continue to flash the userdata.img, blob, and battery.dtb.
Click to expand...
Click to collapse
So I should just flash the ota.zip?
Also i did everything like the guide. I flashed boot to boot, recovery to recovery. The only thing that gave me an error was system. Userdata, blob, and battery also flashed successfully. After that didn't work, I also tried the .bat and that didn't work either. Flashing the 5.0.1 update got my tablet running again.

BlackDave said:
No I wipped internal data since I keep everything on external and it still didn't work.
So I should just flash the ota.zip?
Also i did everything like the guide. I flashed boot to boot, recovery to recovery. The only thing that gave me an error was system. Userdata, blob, and battery also flashed successfully. After that didn't work, I also tried the .bat and that didn't work either. Flashing the 5.0.1 update got my tablet running again.
Click to expand...
Click to collapse
If you can find a full ota.zip for update 1.2.1 I'd try that. I'm not sure why you would be having this issue. The only other things I can say to try is redownloading and rebooting the boot loader (select fastboot protocol) between images in case something funny is happening there. Let us know how you end up doing.
Sent from my HTC M8

Keithn said:
If you can find a full ota.zip for update 1.2.1 I'd try that. I'm not sure why you would be having this issue. The only other things I can say to try is redownloading and rebooting the boot loader (select fastboot protocol) between images in case something funny is happening there. Let us know how you end up doing.
Sent from my HTC M8
Click to expand...
Click to collapse
I flashed the 1.2.1 OTA update and it worked. The first time I tried, I did using the TWRP recovery but for some reason, that recovery fails to flash OTAs, so I went with CWM and flashed the 2.1 update and all worked again. After a while, I got tired of all the issues lollipop gave me so that's why I tried following that guide to downgrade.
In the end, using CWM and flashing the OTA is the best way to go. Thank you all for you help.

At&t 1.27.502.5 Stock system.img or Stock system twrp backup needed!!!

I could really use either one of these files to fix my phone, anybody out there able to help me out? I'm more than willing to pay you for your time/effort!

d34thbl00m said:
I could really use either one of these files to fix my phone, anybody out there able to help me out? I'm more than willing to pay you for your time/effort!
Click to expand...
Click to collapse
Have a look there. You can fin a complete RUU from AT&T
http://www.htc.com/us/support/rom-downloads.html

ouioui01 said:
Have a look there. You can fin a complete RUU from AT&T
http://www.htc.com/us/support/rom-downloads.html
Click to expand...
Click to collapse
I know where to find the RUU files, however that is NOT what I need. Hence the thread title.

d34thbl00m said:
I know where to find the RUU files, however that is NOT what I need. Hence the thread title.
Click to expand...
Click to collapse
I
You can extract from RUU the system.img with RUU decrypt tool from there: http://forum.xda-developers.com/one-a9/development/decrypt-ruu-ruu-decryption-script-htc-t3282562
cheers

ouioui01 said:
I
You can extract from RUU the system.img with RUU decrypt tool from there: http://forum.xda-developers.com/one-a9/development/decrypt-ruu-ruu-decryption-script-htc-t3282562
cheers
Click to expand...
Click to collapse
That thread said you need linux, I have a Surface Pro and can't dual boot, so not sure how to run a linux distro? I have made some progress, I was able to pull rom.zip from an RUU and rename that to 2PQ9IMG.zip and put it on the root of my sdcard. When I rebooted into download mode much to my surprise the RUU ran and was successful. So I reinstalled twrp, but it STILL will not let me wipe data to remove encryption. My /data is unmountable, and every time I try to do a wipe in twrp it returns the error "unable to mount storage". Twrp is also still giving me the "No OS Installed" message when I go to reboot. Is there another way to remove encryption without using linux? Or a way I can setup linux on my Surface? I just need to get root so I can s-off...

d34thbl00m said:
That thread said you need linux, I have a Surface Pro and can't dual boot, so not sure how to run a linux distro? I have made some progress, I was able to pull rom.zip from an RUU and rename that to 2PQ9IMG.zip and put it on the root of my sdcard. When I rebooted into download mode much to my surprise the RUU ran and was successful. So I reinstalled twrp, but it STILL will not let me wipe data to remove encryption. My /data is unmountable, and every time I try to do a wipe in twrp it returns the error "unable to mount storage". Twrp is also still giving me the "No OS Installed" message when I go to reboot. Is there another way to remove encryption without using linux? Or a way I can setup linux on my Surface? I just need to get root so I can s-off...
Click to expand...
Click to collapse
Did you try flashing the A9 boot patcher which is in the TWRP recovery thread (5 in second post). which version of TWRP are you using ?
Cheers

ouioui01 said:
Did you try flashing the A9 boot patcher which is in the TWRP recovery thread (5 in second post). which version of TWRP are you using ?
Cheers
Click to expand...
Click to collapse
No I haven't, I'll check it out. I'm using TWRP 3.0.0.

ouioui01 said:
Did you try flashing the A9 boot patcher which is in the TWRP recovery thread (5 in second post). which version of TWRP are you using ?
Cheers
Click to expand...
Click to collapse
Boot patcher failed, like just about everything I try, and returned with an "unable to mount storage" error. I'm stumped. I think it's weird that an official RUU fails with "os-version in Android-file is missing or invalid" error but rom.zip pulled from an official RUU goes through just fine.

If want get root , device boot into twrp "Wipe/Format Data" then back to "Reboot/recovery" install root.zip.
Sorry my bad english!!

d34thbl00m said:
No I haven't, I'll check it out. I'm using TWRP 3.0.0.
Click to expand...
Click to collapse
There was a bug in twrp 3.0.0. The last release is: Current Stable Version: 3.0.0-1
Install the last release and then try in twrp :Wipe/Format Data. Hope it will work for you...
Cheers