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

Help! I did something to my phone!

Hello there, I have a htc one xl on At&t rooted... it has the hboot 1.14. Everything was fine until yesterday when I tried to flash AOKP. I used flash image gui to flash the boot.img then rebooted to TWRP and wiped rom, wiped everything, then installed the .zip for the boot.img I flashed... It would say android is upgrading and cycled through all the apps but stopped at starting apps... wouldnt go past it for 6 hours. I rebooted and tried to reflash the boot.img, but computer didnt recognize phone, and TWRP showed there was nothing on the sdcard

Juts mount your sd in recovery and drag a Rom over from your computer

J3susisl0rd7 said:
Hello there, I have a htc one xl on At&t rooted... it has the hboot 1.14. Everything was fine until yesterday when I tried to flash AOKP. I used flash image gui to flash the boot.img then rebooted to TWRP and wiped rom, wiped everything, then installed the .zip for the boot.img I flashed... It would say android is upgrading and cycled through all the apps but stopped at starting apps... wouldnt go past it for 6 hours. I rebooted and tried to reflash the boot.img, but computer didnt recognize phone, and TWRP showed there was nothing on the sdcard
Click to expand...
Click to collapse
Sounds like the initial problem was just a bad flash/download. It happens.
Try unplugging your phone, shutting down and restarting into bootloader, then hooking it up.

You flashed an incompatible kernel it sounds like.
Make sure you try flashing the kernel within the ROM
Sent from my One X using Tapatalk 2

Hello everyone! Thanks for the replies. Sorry for the rushed post earlier, was on the way out the door after trying for a while to figure something out. I'd love to send a rom to it, but TWRP shows that I have 0 mb available of storage, and the computer says I must format it to access files or something. I may have forgotten to mention- I think i flashed rohan kernel b6 improperly... used flash image gui then went to recovery and clicked it and hit install ... it hung at installing for a while, and upon reboot the starting apps problem happened, followed by no rom being on there, only being able to access TWRP, and ... well, above things. If I formatted it would I be able to put twrp and everything back on it necessary to make the thing function properly? Orr.... Thanks for any help!
God bless!
P.S. Forgot to add- Not sure why I thought I needed to try to "install" rohan kernel later on in TWRP lol
P.S.S I tried to mount sd card in twrp, nomatter how many times i try to select it it wont work

Yeah just format it and then it'll show up as a drive for you then you can send a rom to it.
Sent from my HTC One XL using xda premium

thejosh86 said:
Yeah just format it and then it'll show up as a drive for you then you can send a rom to it.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
I'm sorry- I really don't understand what I'm going to lose if I format, like... apparently all my data is somewhere in the air now lol, but will I not lose any important things the phone needs to run? TWRP? Will the bootloader still be unlocked?
And, if above "issues" aren't "issues", then will the following steps be correct?
1. Send ROM to phone
2. Throw fastboot.exe and adb thing into a folder with the ROM/ boot.img
3. CMD prompt to flash
4. Magic
?
Thanks so much and sorry to be a pain here if this isn't that big of an issue! I was afraid I bricked the thing, but I was holding on to hope that I didn't since it seemed like a good thing that it would still boot to TWRP.
Also- not sure if this is an issue, I tried to hit adb sideload in TWRP just messing around with options, and it said it couldn't mount the SD card.... so.... yeah, is that an issue?

Whatever data you had on the sd card is gone anyway. You need to reformat to use it.
Formatting the sd card won't affect your /system files or recovery, which are stored on a different area, or cause you to lose root.

You guys are awesome. Thanks so much!
And, as you get a lot: Sorry... for being a noob. lol

[Q] Please help no OS on phone.

I don't know all of the technical language here so I'll just say this as simply as I can.
Wanted to go from stock ICS to a JB rom.
I unlocked the bootloader using the X-Factor 2.20 method.
Then using the All-in-one toolkit I installed the included recovery.
Next I stupidly did not make a recovery file on the phone and tried to flash the boot.img file from a JB rom in the kernel section of the All-in-one tool.
So instead of having a working rom I just have a splash screen and can either boot into the bootloader or go into recovery.
Also when I reboot from recovery it tells me there is no OS installed on the phone.
Now reading through a lot of these roms it seems that the proper way to install is to first backup, then to put the file onto the phone's memory and install through the recovery. Where I am right now I cannot find a way to get any files onto the phone so that I could try that.
Where do I go from here?
Any help would be much appreciated. Thanks.

Boot into recovery by holding power+vol down
Mount usb in twrp
On your computer, go to "my computer" right click on removable storage
Choose format.. This will take some time, so in the meantime download cleanrom 5.1 from your computer
When format is finished, transfer cleanrom onto your phone.
Unmount sdcard in twrp. Now choose install, install cleanrom zip. (It will flash boot.img for you.)
Now you have a stable ROM to work with. Report back when your stable again
Sent from my HTC One XL using Tapatalk 2

I will definitely try that. One thing that I also want to bring up is that the phone goes from the normal HTC white splash screen to one with the HTC logo and red letters "this phone is for developmental purposes only..." does that matter or will it go away with the install of cleanrom?
Edit: Answered my own question. Thank you!

Nope... That what happens when you unlock boot loader. It will never go away till we achieve s-off
Sent from my HTC One XL using Tapatalk 2

[Q] Where Did I Mess Up?

This rooting crap used to be easier man, I swear. I think I literally rooted my Evo through the web browser. Whatever...anyway, it just seemed a lot less riskier back then. I havent had an Android phone since then so I was happy to see my One S come in the mail. Right now though, I'm hoping I didn't waste my money. I'm gonna try to retrace my steps as explicitly as possible so someone can help me easier.
1. Unlocked the bootloader thru HTC Dev
2. Used this to root
3. Install recovery, TWRP.
4. Downloading CM10.2 ROM and Gapps to flash thru TWRP.
5. Cant mount sdCard. The mount screen in TWRP gives you 4 check box options, cant check 'mount sd'
5a. (Can boot phone as normal until now. Was on stock rooted rom with no problems but I hate sense and wanted to switch)
6. Wipe everything; data, cache, dalvik, sd.
7. Cant see SD Card at all now. No OS. Stuck on white HTC startup screen if I dont go to bootloader/recovery.
8. At this point I just tampered around with random solutions from threads I found on google, now I can see my SD card in TWRP file manager but its still not mountable (Even when I could check 'mount sd' windows doesnt see anything).
9. Tried relocking bootloader, running RUU, error code 155.
10. Right now, stuck with tampered unlocked bootloader, s-on, cant install rom because sd card wont mount and cant push ruu because it errors within 2 minutes. This was from last night, and I havent touched it today, and I wont touch it until someone who actually knows what they're doing can tell me whats up.

help
Hi,
I had a similar issue.. I followed a tutorial on YouTube and the guy forgot to mention that the ROM needs to be on the SD before rooting.
And my device was not reconised by my computer (win 7).
I messed around with a few recovery's.. turned out i was using a older version and after flashing about 3 recovery's my computer reconised my device when mounting SD card.
Hope this helps.

cfagan17 said:
This rooting crap used to be easier man, I swear. I think I literally rooted my Evo through the web browser. Whatever...anyway, it just seemed a lot less riskier back then. I havent had an Android phone since then so I was happy to see my One S come in the mail. Right now though, I'm hoping I didn't waste my money. I'm gonna try to retrace my steps as explicitly as possible so someone can help me easier.
1. Unlocked the bootloader thru HTC Dev
2. Used this to root
3. Install recovery, TWRP.
4. Downloading CM10.2 ROM and Gapps to flash thru TWRP.
5. Cant mount sdCard. The mount screen in TWRP gives you 4 check box options, cant check 'mount sd'
5a. (Can boot phone as normal until now. Was on stock rooted rom with no problems but I hate sense and wanted to switch)
6. Wipe everything; data, cache, dalvik, sd.
7. Cant see SD Card at all now. No OS. Stuck on white HTC startup screen if I dont go to bootloader/recovery.
8. At this point I just tampered around with random solutions from threads I found on google, now I can see my SD card in TWRP file manager but its still not mountable (Even when I could check 'mount sd' windows doesnt see anything).
9. Tried relocking bootloader, running RUU, error code 155.
10. Right now, stuck with tampered unlocked bootloader, s-on, cant install rom because sd card wont mount and cant push ruu because it errors within 2 minutes. This was from last night, and I havent touched it today, and I wont touch it until someone who actually knows what they're doing can tell me whats up.
Click to expand...
Click to collapse
Okay First I don't whether you have an S3 version (VilleC2) or an S4 version (Ville).
Understand this, when you format SD card using TWRP recovery, you can't mount it. It is because only the Stock HTC recovery is able to format the SD correctly.
What you ought to do now is:
1. Download stock HTC recovery for your phone version, S3 or S4.
2. flash the recovery through Fastboot using the command:
Code:
fastboot flash recovery recovery.img
3. Go to bootloader and select the option to erase Storage; if it's not there, then you will have to select Factory Reset, wiping your data and apps too.
Regards

Just use this - http://forum.xda-developers.com/showthread.php?t=2471151
It will almost do all things for you, Unlock Bootloader, Flash recovery, Root ...
And remember, if abd console says "error: device not found" or when downloading and fail install "HTC MTP drivers" don't worry, it happened to me too.
Remember, you need flashed Recovery, to be able to Gain Root. And Unlocked Bootloader to flash Recovery.

Now I am back to original stock ROM, rooted.
Windows still not recognizing SD card after mount. it gives option to mount internal_sd, but folder that sd is located is called 'sdcard'? I flashed stock recovery, clear storage, then factory reset, then root, then flash twrp.
Even when I put a custom ROM and gapps on the sd through stock ROM, it bootloops after flash. It's like HTC really doesnt want me to appreciate anything other than their crap stock firmware.

cfagan17 said:
Now I am back to original stock ROM, rooted.
Windows still not recognizing SD card after mount. it gives option to mount internal_sd, but folder that sd is located is called 'sdcard'? I flashed stock recovery, clear storage, then factory reset, then root, then flash twrp.
Even when I put a custom ROM and gapps on the sd through stock ROM, it bootloops after flash. It's like HTC really doesnt want me to appreciate anything other than their crap stock firmware.
Click to expand...
Click to collapse
Rooting the stock is not necessary flash a custom rom. Most roms that you flash are already rooted and root should be flashed in twrp if you just want a stock rooted rom
Flash the stock recovery, clear storage and factory reset. Then flash TWRP. If that doesn't boot for some reason you may need to flash the stock ruu.
If you chose to keep the stock firmware, you can download the superuser.apk from the playstore. When you run the app it will give you the option to reboot into TWRP to flash the root automatically.

mjsheldon4 said:
Rooting the stock is not necessary flash a custom rom. Most roms that you flash are already rooted and root should be flashed in twrp if you just want a stock rooted rom
Flash the stock recovery, clear storage and factory reset. Then flash TWRP. If that doesn't boot for some reason you may need to flash the stock ruu.
If you chose to keep the stock firmware, you can download the superuser.apk from the playstore. When you run the app it will give you the option to reboot into TWRP to flash the root automatically.
Click to expand...
Click to collapse
Even after clear storage, factory reset and TWRP flash I still cannot see the SD card in Windows or install a custom rom without white HTC bootloop. Only way I can mount the SD card is on the stock rom.
Also, Win says SD card is 10GB. Does everything else really use up 6GB?

cfagan17 said:
Even after clear storage, factory reset and TWRP flash I still cannot see the SD card in Windows or install a custom rom without white HTC bootloop. Only way I can mount the SD card is on the stock rom.
Also, Win says SD card is 10GB. Does everything else really use up 6GB?
Click to expand...
Click to collapse
What CID do you have. Have you matched the RUU with the your CID. If the CID's don't match it will give you and error and not flash. If you are SuperCID you can flash any RUU but with a stock CID you need the RUU that matches it.

mjsheldon4 said:
What CID do you have. Have you matched the RUU with the your CID. If the CID's don't match it will give you and error and not flash. If you are SuperCID you can flash any RUU but with a stock CID you need the RUU that matches it.
Click to expand...
Click to collapse
I already flashed RUU. I can't flash a custom ROM.

I don't see here. Are you s-off or on?
Sent from my CM 10.1 Motorola Xoom Wingray!

mjsheldon4 said:
I don't see here. Are you s-off or on?
Sent from my CM 10.1 Motorola Xoom Wingray!
Click to expand...
Click to collapse
On

HELP, did I brick my xoom???

/I had the touch recovery on there and cyanogenmod 10 I think.. worked fine for a year.
Then I wanted to format and start over, so I did a wipe of everything and now anything I try to flash gives me an error, I can still get into the touch recovery but every rom I've tried won't install, keeps saying error.
I'd like to just throw a rom on it and be done, or go back to stock.
Also, when I try to reboot from the touch flash program it tells me its not rooted and would I like to root it now, swipe to confirm or just exit to deny.

Try to rsdlite/sbf to 100% stock
Sent from my dlx using Tapatalk 4

do what? what does that even mean?
thanks

I hope you have your ROM on your sdcard, if so then "Format Data". You'll lose everything on your internal memory but it should solve your ROM errors, considering your ROM isn't the issue to begin with. Especially if you are trying to go from 4.3 back to 4.2. If it's on your internal storage, then you'll need to do alot more searching on how to use adb and fastboot or hope someone is willing to find it for you and post a link.
You might also what to mention what ROMS / version you are trying to install and what version Xoom you have. If you are trying to install the latest EOS Roms they don't work.
And just as every post mentions before flashing something new... do a Nand backup (backup in recovery).
As for your root issues, it's known for 4.3 and has been mentioned many times on these forums. Do some searches about it here or simply go back to 4.2.
The Xoom is pretty hard to brick.

Domunus said:
I hope you have your ROM on your sdcard, if so then "Format Data". You'll lose everything on your internal memory but it should solve your ROM errors, considering your ROM isn't the issue to begin with. Especially if you are trying to go from 4.3 back to 4.2. If it's on your internal storage, then you'll need to do alot more searching on how to use adb and fastboot or hope someone is willing to find it for you and post a link.
You might also what to mention what ROMS / version you are trying to install and what version Xoom you have. If you are trying to install the latest EOS Roms they don't work.
And just as every post mentions before flashing something new... do a Nand backup (backup in recovery).
As for your root issues, it's known for 4.3 and has been mentioned many times on these forums. Do some searches about it here or simply go back to 4.2.
The Xoom is pretty hard to brick.
Click to expand...
Click to collapse
I have nothing on my SD card or Internal Memory, its completely empty!
Every rom I try to flash gives me an error, I tried a few now and it won't work.
I'm at a loss of what to do

I have Twrp recovery ver 2.5.0.0
I tried to flash later version recoveries but I just get an error

what are trying to flash recovery with? should be using fastboot. with an unlocked bootloader, you, quite literally, CANNOT brick the device
also, ignore the idiot who talked about rsd. that would be beyond stupid.
because you can still get into recovery, you can use adb to sideload the ROM.
adb sideload /path/to/ROM.zip
Sent from my Nexus 5

notbrodie said:
what are trying to flash recovery with? should be using fastboot. with an unlocked bootloader, you, quite literally, CANNOT brick the device
also, ignore the idiot who talked about rsd. that would be beyond stupid.
because you can still get into recovery, you can use adb to sideload the ROM.
adb sideload /path/to/ROM.zip
Sent from my Nexus 5
Click to expand...
Click to collapse
Yes I can get into recovery. Where can I read up on how to use adb again?
I'd love to try that.
THANKS

just download the android SDK and pull adb and fastboot executables ( should be in android-tools). as I use Ubuntu, I don't use the SDK any more.
once you have the adb file, if you place it in the same directory as the ROM, you would just need to 1) open command line 2) CD to directory where the files are 3) in Xoom recovery, go to advanced > sideload 4) on computer, type adb sideload ROM.zip
this is will flash the ROM over. do the same thing for gapps. then reboot Xoom
Sent from my Nexus 5

Yea, problem is, what you're saying, makes no sense to me.
I downloaded android SDK installed the 500 meg program.. Now what
also, it seems I cannot get my computer to recognize my xoom.. I downloaded the drivers and all,comes up unknown usb device.
This just really BLOWS!

I went ahead and did some quick searches for you in google. Hope this helps you, if not, do more searches for ADB Sideload xoom rom. If you don't understand something during one of the steps, google it. BTW, you need to update your TWRP if you plan to mess with 4.3.
If you need a visual guide, go to youtube and type in adb sideload. Good luck.
This is a bit old, but it's simplified and may help you setup ADB.
http://www.xoomforums.com/forum/motorola-xoom-hacking-guides/1838-setting-up-adb-windows-7-64-bit-other-windows-platforms.html
This guide may also help you, it's for HTC but obviously change anything HTC related to Xoom. It shows you how to sideload with every detail.
http://forum.xda-developers.com/showthread.php?t=2317985

ok.. does it matter that no matter what I try no computer can recognize my xoom.. Always says unknown device.. I downloaded moto's drivers and everything.
While in recovery and going to mount it still never recognizes my xoom..
Tried in 2 computers, same results