Database Info

HTC One X Flash and SDcard issue

Good Morning,
I have run into a problem with my HOX. After rooting and unlocking, I attempted to flash a custom ROM. Well, in my haste I flashed the new boot.img before transferring the new ROM to the phone. I have now formatted all info in all areas of the phone (wrong move I know). I can boot into fastboot, I can boot into CWM.
The problem lies in the mounting of the SDcard. I read through countless threads and everything I have tried up to this point has netted zero results. I have been flashing since the old Win Mobile days. I have a fairly strong understanding of ADB. I am not a developer, nor do claim to have the knowledge of one. I am reaching out and asking for help. I have CWM, version 5.8.3.1 touch. I also tried flashing back to the original boot.img and still no dice. Perhaps I have missed a step, I hope that is all. I did make a quick post in another thread, but it was made before I read allot of the other threads, so I am double posting. I am open to trying any advice that is offered.
Thank You all so much
Jason

zad2k2 said:
Good Morning,
I have run into a problem with my HOX. After rooting and unlocking, I attempted to flash a custom ROM. Well, in my haste I flashed the new boot.img before transferring the new ROM to the phone. I have now formatted all info in all areas of the phone (wrong move I know). I can boot into fastboot, I can boot into CWM.
The problem lies in the mounting of the SDcard. I read through countless threads and everything I have tried up to this point has netted zero results. I have been flashing since the old Win Mobile days. I have a fairly strong understanding of ADB. I am not a developer, nor do claim to have the knowledge of one. I am reaching out and asking for help. I have CWM, version 5.8.3.1 touch. I also tried flashing back to the original boot.img and still no dice. Perhaps I have missed a step, I hope that is all. I did make a quick post in another thread, but it was made before I read allot of the other threads, so I am double posting. I am open to trying any advice that is offered.
Thank You all so much
Jason
Click to expand...
Click to collapse
1. Wrong section, things like this should be in Q&A
2. Did you flash the CWM recovery with working ADB? If so you should be able to push the rom to your sdcard from recovery (someone correct me if I'm wrong about that).

RUU back to stock?
Sent from my HTC One X using XDA

Enter Fastboot re flash a recovery that has ADB working either teamwins or the CWM that has working ADB. Then push the rom to the sd card through ADB in recovery.

My apologies for posting in the wrong area...Thank you for the quick responses. I reflashed the current CWM, no luck. I flashed the recovery from Teamwin and things are looking up. I was able to look at the sdcard in recovery and I was able to push the ROM to the sdcard via ADB. However, when I try to install the zip, it gives the error again "can't mount sdcard" failed....hmmm Any other ideas or thoughts??
Thank You
Jason

I just wanted to say thank you to those who helped. All the time wasted, I never relocked before trying to flash RUU!!

made same mistake
...everything was too cool to be true,
rooted my HOX with
One Click HTC One X Root by kennethpenn (Win/Mac/Linux) (Recommended)
then
Auto Deodex/Debloat AT&T One X by kennethpenn
then let my HOX relax for a week, but past weekend after install CWM with
How To: Install CWM Recovery on HTC One X (AT&T)
Filed under Development, Guides by Kenneth Pennington
i was not sure about wether to install ROM
CleanROM DE 2.1 -★| Sense / AOSP Blend | Smooth! | Refreshing! |★-
or
CleanROM 2.4.5 SE -★| Landscape! | EQS! | APM! | Clean! |
i download both and then restart in recovery then i did
install zip from sdcard, but instead of do it over CleanROM 2.4.5, I did it with CleanROM DE 2.1
after reboot i realize that i screw it big time since CleanROM DE 2.1 comes without boot.img
so now when i start my HOX just reboot by itself after 5sec, the only thing i am able to do is start on recovery and when i tried to install all over again thru install zip from sdcard i just get
"E: Cant mount /sdcard/"
I ran AT&T RUU_Evita_UL_Cingular_US-1.83.502.exe and RUU 1.73 but it cant detect my HOX
help!!!

I found this for you. Give it a try. It was not my work just googled.
This is for people who have the following problem:
Cannot boot into ROM (e.g Stuck at the HTC Logo)
Boot Loop
Re-locked bootloader while having a non-working ROM
Cannot flash RUU because battery is below 30%
[edit] Try this first
The most common problem is being stuck at the HTC Logo after flashing a ROM, try clearing the fastboot cache with these steps:
Power off your phone and hold the power button + volume down
Choose fastboot from bootloader
Connect the phone to your computer
In command prompt window opened in your platform-tools folder type:
fastboot erase cache
Choose "Reboot" in fastboot menu
If this doesn't work, try the rest of the guide
http://forum.xda-developers.com/wik...very_-_what_to_do_in_the_event_of_a_bad_flash

How to Install ROM via cmd. Stuck in bootloop cannot access SD card via computer.

I've looked through a lot of guides and other peoples similar issues but I need direct help and advice because I think my issues are slightly different to other peoples.
Today I downloaded a lockscreen mod, installed it in 4EXT recovery, rebooted phone and nothing but the top icon bar appeared. so I return to recovery and install a different lockscreen
mod .zip and reboot - this time it comes back onto the 4EXT recovery page.
I tried restoring a Nandroid backup I did 5 days ago but it's gone!
All known details below:
HTC Senasation XE with beats audio
JuopunutBear [Unlocked]
PYRAMID PUT SHIP S-OFF RL
HBOOT-1.27.1111
Radio-11. 24A 3504. 31_M
4EXT Recovery Touch installed and working
Bootloader works
Current issues:
I am stuck in a bootloop. Or to be more descriptive - when I power on my phone it starts up and goes straight into 4EXT Recovery
I cannot access my SD card via my computer due to no ROM working.
I know my phone ain't a brick... yet! So I know this can be fixed.
If my stock ROM no longer loads my conclusion is the [MOD] has altered the system files and corrupted them.
My major mistake here is the fact that I thought I had installed Sense 4.0 but I hadn't and the MOD's were for Sense 4.0
The contents of my SD card are on my computer as a backup, but all other files aren't not that it should matter at this time.
I tried factory reset via bootloader - nothing has happened.
I've read a lot of guides in the past 2 hours. I am currently following this guide: http://forum.xda-developers.com/showthread.php?t=1631861
What I have in mind is if I flash a custom ROM onto my phone then everything should be back to normal. But because I cannot put the .zip onto my phone
via the computer > SD card method I am stuck and can't think what to do next.
I haven't 'wiped' or 'formatted' anything yet.
If I can access the phone using 'Fastboot USB' the next issue is how do I install the Android_Revolution_HD-Sensation_7.1.zip ? Do I type in some code using cmd? If so what do I type in?
If theres a clear step by step guide for this a link is all I need.
I hope I've covered everything to get help. Okay fingers crossed.
{EDIT}
I've restarted my computer and the Fastboot USB works now so that's good news.
Now how to install a .zip using cmd?
{EDIT 2}
I've came across this: http://forum.xda-developers.com/showthread.php?t=1672425&page=18
I've read it all, it makes sense but not going to use it until I get a reply in this thread. If you think I should get RUU please say so.

This should do the trick.

ridder215215 said:
This should do the trick.
Click to expand...
Click to collapse
This looks promising and appears to be the solution to my problem. Thanks for the link. I'll update this thread once I've completed the steps in the guide.
Thankyou!!

Fantastic it worked!!! Phew.
Thankyou ridder215215 you saved me hours.

[Q] Tried to install maximus hd and now cant access sd card

I followed the instructions on the thread. It instructed me to install a new firmware to be up to date.
I assume installing the new firmware reformatted my sdcard.
When I loaded up the rom the first time I dragged the ROM file over to my sdcard.
went back into twrp
wiped system and then went to flash the rom, but there is no sign of the rom file or any other file on my sdcard.
So I unmount to access my sdcard through twrp so I can re-place the file on my sdcard to flash it. but I am unable to access my sd card without "formatting" it. when I open the format options it says 48mb so I assume this will not work.
It wiped all my backups and everything and now I have no way to reformat or access my sd card to put a new rom on it. its only reading 48mb
What do I need to do? any help, thanks.

Try searching before posting a question that's been asked a gazillion times. Even here just a few posts down someone asked the same question.
Sent from my HTC One S using xda app-developers app

rgrpark said:
Try searching before posting a question that's been asked a gazillion times. Even here just a few posts down someone asked the same question.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Oh sweet. thanks for the help. (sarcasm)
The search is down temporarily. (try searching before you give a douchey reply that's been quoted a gazillion times)

As a follow up I think I got it going.
To get my phone going again, I used a ruu and flashed it via fastboot.
I would've tried to push via adb or sideload. but I couldn't get adb to recognize my phone. and I honestly just never used the sideload. that might have worked too.
Before I reinstalled. I changed my cid from tmo_1010 or whatever it was to 11111111.
and I also installed the latest twrp recovery.
The only difference in the flashing process was,
in the instructions on the Maximus HD thread it tells you as the last step in the RUU screen to flash recovery filename.img.
but the file he provides is a .zip file. so use fastboot flash zip filename.zip and got not errors in return.
before it was still loading up the older version of twrp I had on there.
hope this actually helps somebody. If someone wants to chime in explain how to push a file to the sdcard via sideload (or at least give a link) im sure that would help someone else. the search function is down right now so I cant go find one.

[Q]Phone wont boot/Xylon Rom Help Please HTC ONE XL/Evita Telstra

So I Unlocked my bootloader with htcdev.com, used hasoons toolkit to get Team Win Recovery Project, Once again used hasoons tool to get superSU rooted, installed etc. I then made a backup with TWRP, wiped the phone and flashed the Xylon Rom which i downloaded from the OneXRoot website along with the google apps .zip file. I then booted into fastboot and used cmd to flash the boot.img file onto the phone. Now the phone boots into the grey xylon screen but does not get any further, just that flashing white streak that indicates "Loading". I have tried wiping and restoring to the backup i made in TWRP but then it just loades the HTC One screen over and over not booting any OS, I have also tried wiping and re installing the rom with the previous steps to no avail. How should i recover my phone to a usable state? I dont care what Rom/OS is on there i would just like to get it working again.
Any advice would be appreciated greatly.
Kind Regards, Raf.

Did you erase dalvik and cache?
Or you can do an RUU. And next time, use xda as a despot of knowledge. ROMs downloads inclusive
And next time, also post in the q&a section
Sent from my HTC One XL using XDA Premium 4 mobile app

Are you Soff?
I believe Xylon uses the 3.4 kernel which required S off and running the 3.18 RUU beforehand.
Sent from my One X using XDA Premium 4 mobile app

Raff1234 said:
So I Unlocked my bootloader with htcdev.com, used hasoons toolkit to get Team Win Recovery Project, Once again used hasoons tool to get superSU rooted, installed etc. I then made a backup with TWRP, wiped the phone and flashed the Xylon Rom which i downloaded from the OneXRoot website along with the google apps .zip file. I then booted into fastboot and used cmd to flash the boot.img file onto the phone. Now the phone boots into the grey xylon screen but does not get any further, just that flashing white streak that indicates "Loading". I have tried wiping and restoring to the backup i made in TWRP but then it just loades the HTC One screen over and over not booting any OS, I have also tried wiping and re installing the rom with the previous steps to no avail. How should i recover my phone to a usable state? I dont care what Rom/OS is on there i would just like to get it working again.
Any advice would be appreciated greatly.
Kind Regards, Raf.
Click to expand...
Click to collapse
Ok firstly I wouldn't suggest getting ROMs from anywhere except XDA. Other sites (especially OneXRoot) don't properly distinguish between phone models, put simply this leads to bricks. Secondly can you please post your bootloader details, it's pretty standard to do this when asking for help as it gives us the information we need to help you properly.
There could be a few reasons the ROM didn't boot but lets not get into that now. When you created the backup of your stock ROM which boxes did you check? You're s-on so most likely even if you checked the right boxes (system/data/boot) and then restored those partitions later your phone can't flash the boot partition in recovery which means it won't boot. I'd strongly suggest getting s-off, it has many advantages which we can get into once your phone is recovered, and at this stage there's really no reason not to have it.
The best way to recover and get your phone booting right now is just to flash a different ROM. You can download a ROM to your PC and use the mount menu in TWRP recovery to mount your sd card so you can copy it to your phone. If it's aosp just make sure you have the correct version of gapps to correspond with the Android version of the ROM (4.0/4.1/4.2/4.3/4.4). And obviously make sure you flash the boot.img via fastboot after flashing the ROM. Also make sure you perform a full wipe (cache/dalvik/system/factory reset) before flashing any ROM. Before you attempt to flash anything though I need to see your bootloader details as mentioned above, certain ROMs require certain firmware to be installed in order to work.
I mentioned before not to get ROMs from other sites, you actually don't need anything from anywhere except XDA, it literally has everything you'll ever need. The other sites generally just copy/paste from here anyway. Here is our device forum main page:
http://forum.xda-developers.com/forumdisplay.php?f=1538
Here are our two development sections:
http://forum.xda-developers.com/forumdisplay.php?f=1541 (mainly Sense ROMs)
http://forum.xda-developers.com/forumdisplay.php?f=1726 (aosp ROMs)
Here's the q&a section:
http://forum.xda-developers.com/forumdisplay.php?f=1572 (this is where your post should have been created)
Also if you click the Everything Evita link in my signature you'll find that thread extremely valuable. It contains links to basically anything and everything that's of any use.
PS. I'm reporting this thread so the mods can move it to the right section (q&a), please make sure you post in the correct section next time. Thanks!
PPS. Welcome to our forum
Sent from my Evita

timmaaa said:
Ok firstly I wouldn't suggest getting ROMs from anywhere except XDA. Other sites (especially OneXRoot) don't properly distinguish between phone models, put simply this leads to bricks. Secondly can you please post your bootloader details, it's pretty standard to do this when asking for help as it gives us the information we need to help you properly.
There could be a few reasons the ROM didn't boot but lets not get into that now. When you created the backup of your stock ROM which boxes did you check? You're s-on so most likely even if you checked the right boxes (system/data/boot) and then restored those partitions later your phone can't flash the boot partition in recovery which means it won't boot. I'd strongly suggest getting s-off, it has many advantages which we can get into once your phone is recovered, and at this stage there's really no reason not to have it.
The best way to recover and get your phone booting right now is just to flash a different ROM. You can download a ROM to your PC and use the mount menu in TWRP recovery to mount your sd card so you can copy it to your phone. If it's aosp just make sure you have the correct version of gapps to correspond with the Android version of the ROM (4.0/4.1/4.2/4.3/4.4). And obviously make sure you flash the boot.img via fastboot after flashing the ROM. Also make sure you perform a full wipe (cache/dalvik/system/factory reset) before flashing any ROM. Before you attempt to flash anything though I need to see your bootloader details as mentioned above, certain ROMs require certain firmware to be installed in order to work.
I mentioned before not to get ROMs from other sites, you actually don't need anything from anywhere except XDA, it literally has everything you'll ever need. The other sites generally just copy/paste from here anyway. Here is our device forum main page:
http://forum.xda-developers.com/forumdisplay.php?f=1538
Here are our two development sections:
http://forum.xda-developers.com/forumdisplay.php?f=1541 (mainly Sense ROMs)
http://forum.xda-developers.com/forumdisplay.php?f=1726 (aosp ROMs)
Here's the q&a section:
http://forum.xda-developers.com/forumdisplay.php?f=1572 (this is where your post should have been created)
Also if you click the Everything Evita link in my signature you'll find that thread extremely valuable. It contains links to basically anything and everything that's of any use.
PS. I'm reporting this thread so the mods can move it to the right section (q&a), please make sure you post in the correct section next time. Thanks!
PPS. Welcome to our forum
Sent from my Evita
Click to expand...
Click to collapse
Hi, thanks for the tips about Son/Off I plan on doing that later,I figured out i could put a new rom on using the mount function in TWRP, I successfully loaded cyanogen nightly onto my phone and it is working great, however i flashed the gapps aswell but when I booted my phone i had to manually install the play store, maps, and other google services. When i made a backup I believe i ticked all the correct boxes, and i always cleared the cache, etc.
Thanks for all the help so far.
Raff.

You had to install Play Store? Or you had to install apps from the Play Store? Which ROM and which gapps package did you flash?
Sent from my Evita

timmaaa said:
You had to install Play Store? Or you had to install apps from the Play Store? Which ROM and which gapps package did you flash?
Sent from my Evita
Click to expand...
Click to collapse
I installed CM10.2 Nightly (The .zip is called cm-10.2-20130821-NIGHTLY-evita) and gapps 4.3, I got these from the OneXRoot site unfortunately. I did this before I checked on the thread again and saw that these other sites were not the best/reliable things to use. I had to install the play store from my browser, I just googled play store download and installed it, then proceeded to install all my other apps.

Ahh ok, I see. As far as I know the best place to get gapps from is the goo.im gapps page. I'm not sure if they have 4.4 gapps up yet but they're fairly easy to find with Google.
Sent from my Evita

[Q] Mount USB Storage not working from Recovery

I have a weird issue occurring, and am apparently not alone - but what worked for others has not worked for me.
I decided to try out the new CandyKat ROM and wanted to "clean" the phone first (it's been awhile since the last uncluttering). I ran the AT&T Stock 3.18 RUU and then decided to upgrade to the latest TWRP 2.7.0.0 as well. However, after flashing the 2.7.0.0 recovery, I found that I was unable to mount the SD card to copy over the new ROM and Gapps. I had already done a full wipe, so I re-ran the stock RUU and tried again just with a factory reset - same results. I searched the forums for a while and found another thread in Q&A regarding the same issue, but going back to TWRP 2.6.3.x solved the problem for the other user. I flashed the unofficial TWRP 2.6.3.0 w/ SELinux (which is what I had prior to updating to 2.7.0.0), but still had the same issue. The weird thing is that I can mount USB storage from within the ROM and it works just fine. But, from within the recovery, it will say the USB mount successful, but Windows will not recognize the device and bring up the sd card storage. The phone is recognized in Device Manager, but I have no options to explore the SD card.
I've tried several things, all to no avail:
- uninstalled HTC Sync, then downloaded and installed latest version from HTC's website (thinking it might be a driver issue)
- tried to mount, no luck
- updated hboot to 2.18
- tried to mount, no luck
- downgraded hboot from 2.18 to 2.15
- tried to mount, no luck
- uninstalled phone from Windows Device Manager, then unplugged and plugged phone back in (Windows will recognize the Android phone in Device Manager, but will not access the internal storage)
- tried to mount, no luck
Everything was working correctly until I updated to TWRP 2.7.0.0 earlier today. All ADB and fastboot functionality still works fine. I find it very odd that I can mount USB storage all day long while the ROM is running, but not from recovery. I am at a loss on what else to try and am down to two options: (1) using fastboot to erase the current recovery before flashing a new one, or (2) letting Windows reformat my internal storage.
Thoughts? Suggestions? I am out of ideas other than the two above...
Mark
HTC One X (AT&T)
hboot 2.15
S-OFF and Unlocked
SlimKat Unofficial Beta 2.3

To be honest I have never seen this issue before.. so we will check every detail of your flash.
Did you check md5 of the recovery's prior to flashing?
Did you do a fastboot erase cache after flashing the custom recovery?
While you answer these questions, I will see if I can recreate the issue myself. I don't run windows though so if something to do with the OS is the problem, I surely won't be able to recreate it.

No, I did not check the MD5 of 2.7.0.0. The other two recoveries I have tried are from prior downloads stored on my computer that have worked fine prior to the flash today.
Yes, I did do a fastboot erase cache.
I appreciate the help and inquiries...
-Mark

mawoods75 said:
No, I did not check the MD5 of 2.7.0.0. The other two recoveries I have tried are from prior downloads stored on my computer that have worked fine prior to the flash today.
Yes, I did do a fastboot erase cache.
I appreciate the help and inquiries...
-Mark
Click to expand...
Click to collapse
There's another thread already discussing the problem you're facing, if you search our forum you'll find it along with the solution that's been posted.
Sent from my Evita

timmaaa said:
There's another thread already discussing the problem you're facing, if you search our forum you'll find it along with the solution that's been posted.
Sent from my Evita
Click to expand...
Click to collapse
damnit, I just flashed and tested it for nothing lol Was working fine for me though.

timmaaa said:
There's another thread already discussing the problem you're facing, if you search our forum you'll find it along with the solution that's been posted.
Sent from my Evita
Click to expand...
Click to collapse
Thanks, but searching was the first thing I did. If you are referring to this thread, or this one, those are what led me to try two of the things I tried (reverting back to an older recovery, which was a no-brainer, and trying to uninstall and reinstall through Windows Device Manager). Unfortunately, none of the things mentioned in those threads worked for me.
I was finally able to resolve the issue, though, just a little while ago. I re-ran the 3.18 stock RUU, then let Windows format my internal storage. After which, I ran the stock RUU again, pushed recovery switcher to my phone, and then flashed the modified 2.6.3.0 from within Recovery Switcher. It took about 30 seconds, but Windows finally recognized the phone when I mounted USB storage from recovery.
I was seeing a couple of weird things throughout it all, like getting [remote not allowed] when trying to "fastboot erase recovery", even though other fastboot commands worked fine, including the devices command. Also, would periodically get a "unable to mount \cache" when formatting within recovery. Oh well, after the Windows re-format of the SD, everything seems to be working fine. I appreciate everyone's assistance and suggestions.
-Mark