After getting the last week's CyanogenMod onto my at&t one x, my USB mass storage doesn't work. All that happens is I click "turn on mass storage" but it doesn't show up on the computer in a drive nor logging in usb storage.
My drivers are up to date. And I flashed a newer cm but it hasn't changed...
Please help
It's more likely to be your pc than your phone that's causing the issue. Also, sometimes it takes a minute for it to come up and lastly, if you want to be certain.
Make sure you're using twrp 2.3.3.1 or under or 2.6. All versions in between have issues wiping.
Check the md5 of your rom zip file to make sure there was no corruption.
Lastly make sure to do at least a factory reset though wiping system doesn't hurt either.
If you've done all that and you're still having issues try another usb cord and usb port.
Sent from my One X using xda app-developers app
Thanks so much. I'm waiting to get back home to see if this works. Should I reinstall HTC drivers?
Uninstall any HTC drivers and software and install the latest HTC sync just in case.
Sent from my One X using xda app-developers app
Nope. nothing is working. i think its time to figure out AirDroid...I wonder if its the 3.4 kernel issue though?
No or way more people would have the issue than just u.
Did you factory reset in bootloader at some point?
Sent from my One X using xda app-developers app
Yeah I did. Speaking of kernels, what are some compatable kernels for cm Evita?
pandasa123 said:
Yeah I did. Speaking of kernels, what are some compatable kernels for cm Evita?
Click to expand...
Click to collapse
you corrupted your sd card by doing so. you will need to reformat your sd card. as far as custom kernels the "search" function is your friend
I wouldn't trust any custom 3.4 kernels just yet if that's what you mean. It's still in beta and has weird issues so any modifications made could intensify instability and even cause permanent damage.
Sent from my One X using xda app-developers app
exad said:
I wouldn't trust any custom 3.4 kernels just yet if that's what you mean. It's still in beta and has weird issues so any modifications made could intensify instability and even cause permanent damage.
Click to expand...
Click to collapse
Yeah unfortunately is hard bricked due to my stupidity. Trying to put a kernel on my phone, the internal storage got delete
oh well. its time to hit up at&t to help me fix it (which they won't be able to) or replace it
pandasa123 said:
Yeah unfortunately is hard bricked due to my stupidity. Trying to put a kernel on my phone, the internal storage got delete
oh well. its time to hit up at&t to help me fix it (which they won't be able to) or replace it
Click to expand...
Click to collapse
hold your horses...your phone still turns on right ? so you should still able to get into recovery ?? if so you're far from a hard brick.
Crappyvate said:
hold your horses...your phone still turns on right ? so you should still able to get into recovery ?? if so you're far from a hard brick.
Click to expand...
Click to collapse
Nope...Unable to either...but lets suppose I was able to be in recovery, what would do I do if my entire storage is deleted? If it doesn't connect to the computer?
pandasa123 said:
Nope...Unable to either...but lets suppose I was able to be in recovery, what would do I do if my entire storage is deleted? If it doesn't connect to the computer?
Click to expand...
Click to collapse
When you say storage people assume you mean the SD card storage.
If your phone is just black screen but gets detected from your PC as QHSUSB_DLOAD then the emmc partition table might be wiped. The only way to know for sure is to try and enumerate your partitions as in the unbrick evita thread. If you don't get a bunch of partitions then the partition table is gone and only JTAGG or motherboard replacement will work.
Unbrick evita:
http://forum.xda-developers.com/showthread.php?t=1966850
exad said:
When you say storage people assume you mean the SD card storage.
If your phone is just black screen but gets detected from your PC as QHSUSB_DLOAD then the emmc partition table might be wiped. The only way to know for sure is to try and enumerate your partitions as in the unbrick evita thread. If you don't get a bunch of partitions then the partition table is gone and only JTAGG or motherboard replacement will work.
Unbrick evit:
http://forum.xda-developers.com/showthread.php?t=1966850
Click to expand...
Click to collapse
It doesn't get detected by PC at all. I tried adb device searching it thorough my terminal, but it just waits for device and doesn't charge either.
pandasa123 said:
It doesn't get detected by PC at all. I tried adb device searching it thorough my terminal, but it just waits for device and doesn't charge either.
Click to expand...
Click to collapse
I would try the unbrick evita thread if I were you just to see. If the PC doesn't detect it at all. It's likely a power issue or the board is physically dead. But that's rare.
exad said:
I would try the unbrick evita thread if I were you just to see. If the PC doesn't detect it at all. It's likely a power issue or the board is physically dead. But that's rare.
Click to expand...
Click to collapse
The battery is unfortunately dead so it won't power on at all. No worries though, since a replacement is arriving soon. I don't want to run into this again, so I'll take a read through it
I can confirm this issue, and I have CM10 (Android 4.1.2).
When I go to Settings > Storage > Menu: Computer connection, the Mass storage is checked, but if I want to change, the Settings will crash (Unfortunately, the Settings has been stopped.)
If you know any workaround, how to use that, please inform me!
Ps. What about the developer options? Couldn't the USB debugging cause this issue?
Try a newer build and completely delete and reinstall your HTC drivers. USB debugging wouldn't be a problem because that's only used for ADB instead of Mass storage
Edit: you know, the CM thread would be better next time, or even a new thread. We opened up a 4.5 month old thread.
Sent from my One X using Tapatalk
Yeah, it works, thank you... Windows sucks...
Related
Hi guys, a little background :
I S-Off'd my Desire S a few weeks ago and installed/clicked gingerbread which i gather roots it?
One day my screen went blank randomly with just the notification bar showing up top. No buttons worked, couldn't turn it off etc.. so I did a battery pull. It then got stuck on the HTC screen, so I googled, tried clicking recovery/factory reset etc.. all while not really knowing what i was doing, but in the end it randomly loaded after a long wait.
Phew, or so I thought.
Now it constantly crashes, turns itself off, the camera doesn't work, force closes galore.. it's a mess. Figured the battery pull messed something up.
Searched a bit more and figured i should try and flash a ROM which might fix it and get it stable again.
Tried installing using 'download ROM' in Rommanager, it did all the installing and whatnot, but when it rebooted nothing had changed. Tried three times, same deal. Figure I should install a ROM via the SD card instead.
Found this forum and a relatively simple/safe guide :
I'm using the guide here : How to flash a perfect ROM.
http://forum.xda-developers.com/showthread.php?t=1257731
The Rom is MIUI.
However, I'm only on step 2 : Format data. (Formatting /system was fine)
Clockworkmod says Formatting /data for about 5 minutes, then : Error formatting /data.
Help!
A big thanks in advance.
Spare yourself a lot of troubles - use RUU and start fresh...
Sent from my HTC Desire S using XDA App
Could be a faulty eMMC chip on the phones motherboard, these tend to break after a few bad battery pulls?
If installing a new ROM on the phone wont work and you get data format problems I would do as posted above. If this doesnt work I would suggest a faulty eMMC chip.
amidabuddha said:
Spare yourself a lot of troubles - use RUU and start fresh...
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
Is there a fairly easy to follow guide that includes every step on here?
According to the FAQ I might have a fried chip.. the e:Unable to mount errors.
Can I still save it with the RUU?
I'm clueless, and a fair few of the guides are not too noob friendly tbh, could you please point me in the direction of an easy to follow guide?
I wish I knew how deadly the battery pulls would be before hand, but when your phone is frozen and you can't power it off, it seems logical. Arrrghg.
Much appreciated.
wax_addict said:
Is there a fairly easy to follow guide that includes every step on here?
According to the FAQ I might have a fried chip.. the e:Unable to mount errors.
Can I still save it with the RUU?
I'm clueless, and a fair few of the guides are not too noob friendly tbh, could you please point me in the direction of an easy to follow guide?
I wish I knew how deadly the battery pulls would be before hand, but when your phone is frozen and you can't power it off, it seems logical. Arrrghg.
Much appreciated.
Click to expand...
Click to collapse
Since you still can boot into your system you are good.
Download the RUU that is right for you from here. Connect your phone to the PC and run the RUU.exe. It will hadle everything automatically. Then you will be back to Stock. To go back to custom ROM:
1) use Revolutionary
2) no need of Gingerbreak since you will flash a rooted ROM
3) flash custom ROM from recovery
amidabuddha said:
Since you still can boot into your system you are good.
Download the RUU that is right for you from here. Connect your phone to the PC and run the RUU.exe. It will hadle everything automatically. Then you will be back to Stock. To go back to custom ROM:
1) use Revolutionary
2) no need of Gingerbreak since you will flash a rooted ROM
3) flash custom ROM from recovery
Click to expand...
Click to collapse
Ok, I have the RUU downloaded.
Should I just connect the USB cable to the phone while it's in ClockworkMod, HBOOT, or does it not matter?
Soooo.. plug in USB cable, run the RUU file in Windows.. should work?
Cheers again.
wax_addict said:
Ok, I have the RUU downloaded.
Should I just connect the USB cable to the phone while it's in ClockworkMod, HBOOT, or does it not matter?
Soooo.. plug in USB cable, run the RUU file in Windows.. should work?
Cheers again.
Click to expand...
Click to collapse
Yep. If by any chance the RUU installer says that it cannot detect your device go to Settings -> Development - > enable USB Debugging on your phone
amidabuddha said:
Yep. If by any chance the RUU installer says that it cannot detect your device go to Settings -> Development - > enable USB Debugging on your phone
Click to expand...
Click to collapse
Cheers. Yep, I got no phone detected, check your USB cable etc.. / ERROR [170] USB CONNECTION ERROR
I can't get into the phone to go into settings and turn USB debugging on though As soon as I get it functioning to that degree I'm not using it for anything other than calls in case I break it again. sadly, I could have earlier before I tried flashing a new ROM. Hindsight eh?
All I can get is HBOOT/ClockworkMod.
Tried RUU with the HTC white screen on and also while in Clockwork Mod.
Anything else I could try?
Thanks.
Are you using windows?
If yes download HTC sync and instal it, could be a missing driver.
Swyped from my Desire S
wax_addict said:
Cheers. Yep, I got no phone detected, check your USB cable etc.. / ERROR [170] USB CONNECTION ERROR
I can't get into the phone to go into settings and turn USB debugging on though As soon as I get it functioning to that degree I'm not using it for anything other than calls in case I break it again. sadly, I could have earlier before I tried flashing a new ROM. Hindsight eh?
All I can get is HBOOT/ClockworkMod.
Tried RUU with the HTC white screen on and also while in Clockwork Mod.
Anything else I could try?
Thanks.
Click to expand...
Click to collapse
From the power menu in ClockworkMod reboot to bootloader (hboot) and with the volume key go to FASBOOT (then you should see "FASTBOOT USB"). Then run the RUU again. Let me know is it working please because I will leave my PC soon
amidabuddha said:
From the power menu in ClockworkMod reboot to bootloader (hboot) and with the volume key go to FASBOOT (then you should see "FASTBOOT USB"). Then run the RUU again. Let me know is it working please because I will leave my PC soon
Click to expand...
Click to collapse
It worked, can't thank you enough!!
Cheers all.
wax_addict said:
It worked, can't thank you enough!!
Cheers all.
Click to expand...
Click to collapse
Good to know
Congratulations!
great to read another XDA forum rescue complete successfully!
Please update post#1 (using Go advanced edit) and prefix the post title with [SOLVED] to indicate that the problem is resolved.
Tectas said:
Are you using windows?
If yes download HTC sync and instal it, could be a missing driver.
Swyped from my Desire S
Click to expand...
Click to collapse
Limited to 5 thanks a day but I'll come back, this definitely helped I'm sure, fairly certain the drivers were needed.
wax_addict said:
Limited to 5 thanks a day but I'll come back, this definitely helped I'm sure, fairly certain the drivers were needed.
Click to expand...
Click to collapse
If your intending on re-running revolutionary to S-OFF your device again then you must first de-install the program HTC SYNC from your PC, don't worry the drivers are left behind and there are all that you need.
This is already the 4th case that the "E: cannot open...." error is successfully solved. I am keeping track on all such posts constantly and in my opinion if we have some more evidences for solved errors of this kind it will be good to remove the "[solved]BRICKed: inside eMMC's dead..." thread to avoid stressing the users...
I think this is a mistake of a service technician that was too lazy to diagnose and just replaced the chip...and started a great panic in this forum
Could be true.
I personally think there where a few devices out there with an chip failure, but most of the reported faults where wrong classified and could have been solved other ways.
Maybe it would be good to write the conclusion at the overall section down, cause our device isn't the only affected.
Swyped from my Desire S
Tectas said:
Could be true.
I personally think there where a few devices out there with an chip failure, but most of the reported faults where wrong classified and could have been solved other ways.
Maybe it would be good to write the conclusion at the overall section down, cause our device isn't the only affected.
Swyped from my Desire S
Click to expand...
Click to collapse
I will write a "calming" thread besides the Guide that is in my signature or as a part of it, just waiting for more confirmations that generally the chip is not affected when there is an error. But it seems not much people are reading the guides they prefer to start a new thread...Anyway I have a friend that is working at a centre of a Mobile Operator for my country and according to him among the hundreds (!) Nokia's, Samsung's, etc., he got only one faulty HTC for repair for the last 2 years (and there is a practice to replace rather than repair as well)
amidabuddha said:
This is already the 4th case that the "E: cannot open...." error is successfully solved. I am keeping track on all such posts constantly and in my opinion if we have some more evidences for solved errors of this kind it will be good to remove the "[solved]BRICKed: inside eMMC's dead..." thread to avoid stressing the users...
I think this is a mistake of a service technician that was too lazy to diagnose and just replaced the chip...and started a great panic in this forum
Click to expand...
Click to collapse
Good point although hopefully any new user experiencing this problem for the first time will create a post in this forum and can get pointed in the right direction, or better still there's always the hope that they will look at the INDEX/GUIDES themselves and read some of the resources that have been made available for them to use.
Possibly create a list of most likely resolution strategies in a new thread so that they can be tried in order and I'll refer users to that in the section on eMMC issues at the bottom of the INDEX thread, where I've tried not to scare users into thinking that its all too late and its game over in the textual intro bit!
ben_pyett said:
...
Possibly create a list of most likely resolution strategies in a new thread ...
Click to expand...
Click to collapse
Yep. My "[GUIDE] Read this before going for eMMC replacement" is updated with the solutions that worked so far..
I was one of the unlucky testers before Steve0007 closed the thread. Did anyone figure out how to save our Sensation after the bad flash? My phone does not light up or respond to any button presses but when plugged into the computer it is recognized as an "unrecognized device."
I guess this is the risk we run being early testers. Hopefully someone figures it out otherwise I've got myself very expensive paper weight.
I assume no two button rescue? And this should be in q/a or general
Can you get to the bootloader?
Sent from my Sensation using xda premium
what did he brick people's phones with what was it supposed to be?
Wrong section. And that happened to me when i got an hd2 and i bricked it. Luckily it was 2 days after i bought it so tmobile gave me another because they thought something was wrong with it. But next time please post in the right section. Thanks.
nba1341 said:
what did he brick people's phones with what was it supposed to be?
Click to expand...
Click to collapse
Its probably only a soft brick
Sent from my Sensation using xda premium
Thank god I didn't flash it, I just finished downloading it when people started reporting issues.
Anyway, I'm sure he didn't mean for it to happen. If you have a spare battery, have you tried putting that one in?
These things are usually flash at your own risk.
I would never flash a ruu, unless it's official it could cause problems.
Sent from my Sensation using Tapatalk
Also, if it doesnt work and if you have tmo. Tell them bs and they will get you one. Just some advice and please dont flame me.
tried spare battery. same result. And i'm sure he didn't do it maliciously I've flashed many of his things before with no problem. Just hoping to get some help. Phone doesn't respond. Can't get to bootloader. Only sign of life is windows recognizing that i plugged something into the usb slot.
Yes as I said, this happened to me exactly when i had a tmo HD2 and flashed a european ruu and it was dead. I tried everything. You will have better luck to talk to your insurance company.
Have you got ADB installed on your pc? If not start downloading and installing it. I will find some links, in just a sec.
Edit:
New to ADB CLICK HER
More to set up path CLICK HERE
http://www.mediafire.com/?rrwi4f258lie1r7
Extract to system 32 or sysWOW64 (64bit)
Try 3 finger salute (VOL UP,VOL DOWN + POWER) with your phone plugged into pc and pc volume up see if it makes a sound like a device has connected.
Whats was this RUU anyway?
if you just need ADB you dont need all of the stuff above or to set up a path if its extracted to those folders
duychau said:
tried spare battery. same result. And i'm sure he didn't do it maliciously I've flashed many of his things before with no problem. Just hoping to get some help. Phone doesn't respond. Can't get to bootloader. Only sign of life is windows recognizing that i plugged something into the usb slot.
Click to expand...
Click to collapse
This is excatly what happened to me.Computer wont see the phone though,so no adb fix can be applied.Mnn i'm so pissed as i dont have insurance.
usually blagging HTC will do the trick for a repair,dont mention XDA, ROOT, ICS or basically anything except your phone said update was available and the battery died
Click to expand...
Click to collapse
roflcopter is 10chars
duychau said:
tried spare battery. same result. And i'm sure he didn't do it maliciously I've flashed many of his things before with no problem. Just hoping to get some help. Phone doesn't respond. Can't get to bootloader. Only sign of life is windows recognizing that i plugged something into the usb slot.
Click to expand...
Click to collapse
What does it recognize it as?
unrecognized usb device
Ok guys, it looks like the firmware that I posted to another thread from 3.06 bricked few devices. I have flashed it and it worked fine, so i tried again with the package i posted and indeed it is corrupted as it bricked also mine
My device does not respond, so I would think it is dead
I feel sorry for those who have bricked also theirs based on the package i posted.
I am closing my Rom thread and starting now my Rom developments will be for my own use. I will not publish anymore my work.
Again I feel sorry for those who have lost their devices.
Steve
ok so now his rom thread is closed. Why not keep it open and work together to help those with bricked devices attempt to restore them to a working state?
That way you keep your reputation rather than running away after bricking devices?
Arrrggghhhh,This could not have come at a worse time
nba1341 said:
ok so now his rom thread is closed. Why not keep it open and work together to help those with bricked devices attempt to restore them to a working state?
That way you keep your reputation rather than running away after bricking devices?
Click to expand...
Click to collapse
Because as far as I know no way to get them back
I'm not sure if this is the right section or not, sorry if it's not, but my phone is really screwed up. I have the htc one S on T mobile that is running the viper one s rom on cwm 10 and will just go to a black screen after displaying the htc screen. I don't have any nandroid backups or copies of working roms either, so I can't boot from those. I did not have USB debugging checked before my phone became corrupt, so I'm pretty sure that ABD will not work, and whenever I try and plug my phone into the computer and access the flash boot menu, it will say that the USB is corrupt and it will not work. The cause of this is because I was messing with the build.prop, I accidentally deleted it, although I have a backup, there is no way if installing it in my phone's current state. It's getting to the point where I honestly don't care if I lose al of my stuff just as long as my phone will work again. Any knowledge shared on this subject would be greatly appreciated. Thanks in advance!
fearthecookie said:
I'm not sure if this is the right section or not, sorry if it's not, but my phone is really screwed up. I have the htc one S on T mobile that is running the viper one s rom on cwm 10 and will just go to a black screen after displaying the htc screen. I don't have any nandroid backups or copies of working roms either, so I can't boot from those. I did not have USB debugging checked before my phone became corrupt, so I'm pretty sure that ABD will not work, and whenever I try and plug my phone into the computer and access the flash boot menu, it will say that the USB is corrupt and it will not work. The cause of this is because I was messing with the build.prop, I accidentally deleted it, although I have a backup, there is no way if installing it in my phone's current state. It's getting to the point where I honestly don't care if I lose al of my stuff just as long as my phone will work again. Any knowledge shared on this subject would be greatly appreciated. Thanks in advance!
Click to expand...
Click to collapse
So... that's miserable. You may put a ROM in your phone SD card and install it using ClockworkMod Recovery.
See this link: http://forum.xda-developers.com/wiki/HTC_One_S#Guides.2FHow_to
Kou Dou said:
So... that's miserable. You may put a ROM in your phone SD card and install it using ClockworkMod Recovery.
See this link: http://forum.xda-developers.com/wiki/HTC_One_S#Guides.2FHow_to
Click to expand...
Click to collapse
Yeah I know that that would fix it, but my main problem is that I don't know how I would get a transfer a rom onto my phone...
Have you found a solution yet too your problem?
You can Trust me I'm a Newb... Sent from my World War II bunker In an undisclosed location.
ElephantThong8 said:
Have you found a solution yet too your problem?
You can Trust me I'm a Newb... Sent from my World War II bunker In an undisclosed location.
Click to expand...
Click to collapse
Nope... Know any pros?
Are you able to boot into recovery okay?
You can Trust me I'm a Newb... Sent from my World War II bunker In an undisclosed location.
ElephantThong8 said:
Are you able to boot into recovery okay?
You can Trust me I'm a Newb... Sent from my World War II bunker In an undisclosed location.
Click to expand...
Click to collapse
Recovery and fastboot and that's about it.
Get a micro sdcard or if you have one already, get a micro sdcard reader, open case from back of your phone and take out the microsdcard.
Put it in the card reader. Copy the rom/image... put the card back in... boot in recovery... use the rom from sdcard to flash that rom.
Have fun..
Sent from my SGH-T889 using xda app-developers app
fearthecookie said:
Yeah I know that that would fix it, but my main problem is that I don't know how I would get a transfer a rom onto my phone...
Click to expand...
Click to collapse
Hey! Read these guides that will teach you how to flash recovery and ROMs.
http://forum.xda-developers.com/wiki/ClockworkMod_Recovery
https://www.xda-developers.com/tag/clockwordmod-recovery/
https://sites.google.com/site/teamr...lopment/flash-clockwork-recovery-via-fastboot
Good luck!
heart_crafter said:
Get a micro sdcard or if you have one already, get a micro sdcard reader, open case from back of your phone and take out the microsdcard.
Put it in the card reader. Copy the rom/image... put the card back in... boot in recovery... use the rom from sdcard to flash that rom.
Have fun..
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Unfortunately, I have the HTC one s,with no removable SD card...
Kou Dou said:
Hey! Read these guides that will teach you how to flash recovery and ROMs.
http://forum.xda-developers.com/wiki/ClockworkMod_Recovery
https://www.xda-developers.com/tag/clockwordmod-recovery/
https://sites.google.com/site/teamr...lopment/flash-clockwork-recovery-via-fastboot
Good luck!
Click to expand...
Click to collapse
Will do!
The last link might help, but whenever I plug my phone into the computer,it says that it is corrupt and will not work
fearthecookie said:
The last link might help, but whenever I plug my phone into the computer,it says that it is corrupt and will not work
Click to expand...
Click to collapse
Well... the only suggestions I can give you now are:
1. Go to this forum to ask for more help.
http://forum.xda-developers.com/forumdisplay.php?f=1528
2. Visit HTC's official websites to find some solutions.
3. Search for other tutorials about flashing recovery via fastboot.
fearthecookie said:
The last link might help, but whenever I plug my phone into the computer,it says that it is corrupt and will not work
Click to expand...
Click to collapse
Have you tried a different port or a different pc?
Take a sceenshot where it says it is corrupt.
Sent from my SGH-T889 using Tapatalk 2
heart_crafter said:
Have you tried a different port or a different pc?
Take a sceenshot where it says it is corrupt.
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
Ok,I'll upload a screenshot, but as for a different pc, I only have my laptop. Different usb ports don't seem to have any effect though...
Hello,
I had a few issues with my HTC One XL, and decided to take the plunge and factory restore my phone. There was nothing that I could think of that I wanted other than my photos, so I backed up all my photos to my PC, and got to restoring it.
Once it was done I realised that I had notes I wish to keep. These notes were quite important to me. Is there any way to get these notes back? My phone is not rooted and on Android 4.2.2. This wouldn't be such a hassle if my phone wasn't running in MTP when I plug it into my computer.
Any help is appreciated,
Thank you.
P.S I'm new when it comes to phone terminology so excuse any silly questions, or if I don't understand what you're saying.
P.P.S Sorry if this is in the wrong forum, I'm 90% sure it's not. I have been up all night trying to figure this out and this is my last hope.
There are data recovery programs available for Windows that might be able to recover your data, but if you've written to the sd card since the wipe those chances are slimmer.
Sent from my Evita
timmaaa said:
There are data recovery programs available for Windows that might be able to recover your data, but if you've written to the sd card since the wipe those chances are slimmer.
Sent from my Evita
Click to expand...
Click to collapse
I have tried around 4 or 5 recovery programs. They are unable to continue as they require the device to be in USB mass storage mode. My phone won't do that because it constantly goes through MTP.
I have not written ANYTHING to the SD card since.
The only way I can think of to get it to mount in usb mass storage mode is through a custom recovery, for which you'd need an unlocked bootloader.
Sent from my Evita
timmaaa said:
The only way I can think of to get it to mount in usb mass storage mode is through a custom recovery, for which you'd need an unlocked bootloader.
Sent from my Evita
Click to expand...
Click to collapse
With an unlocked bootloader, that deletes absolutely everything, doesn't it?
It deleted texts/call logs etc but it left all my photos and music alone.
Sent from my Evita
timmaaa said:
It deleted texts/call logs etc but it left all my photos and music alone.
Sent from my Evita
Click to expand...
Click to collapse
Anyway I could back up the deleted note files? Or something?
Should I just do it and hope to God it doesn't rid of it haha?
I'd at least try it. Look at it this way, if you don't try your data is gone, if you try and it fails your data is still gone but at last you have a chance at restoring it.
Sent from my Evita
timmaaa said:
I'd at least try it. Look at it this way, if you don't try your data is gone, if you try and it fails your data is still gone but at last you have a chance at restoring it.
Sent from my Evita
Click to expand...
Click to collapse
Good advice, just rooted it seeing how it goes.
Blaizen88 said:
Good advice, just rooted it seeing how it goes.
Click to expand...
Click to collapse
Well now my phone won't turn on at all, it is doing something as the computer is saying that it's picking up a USB but can not recognise it.
Screen is black.
What were you doing directly before this happened? Is the device registering on the PC as anything? Perhaps QHSUSB_DLOAD? I certainly hope not.
Sent from my Evita
timmaaa said:
What were you doing directly before this happened? Is the device registering on the PC as anything? Perhaps QHSUSB_DLOAD? I certainly hope not.
Sent from my Evita
Click to expand...
Click to collapse
Don't say that to me. I'm pretty sure I just read QHSUSB_DLOAD in the Device Installing thing on Windows.... I'll double check if I can.
Oh dear, QHSUSB_DLOAD means a brick. What had you done/attempted beforehand?
Sent from my Evita
Yep, just double checked and it's QHSUSB_DLOAD.
I was on what I believe is the last step of rooting it. Unlocked the bootloader and flashed a custom recovery. Just went to enter recovery the last time and it didn't turn back on.
Which recovery did you flash? What's the exact filename?
Sent from my Evita
Knowing me it's problem wrong, I tried to do as much research as I could...
openrecovery-twrp-2.6.3.0-endeavoru.img
It did boot after I flashed it though.
(Sorry if it takes a while to reply, I have to wait 5 minutes between them due to being a newcomer)
Oh no. That's a recovery for the HTC One X. The Endeavoru part of the filename means HTC One X (it's the codename). The codename for the HTC One XL is Evita. There's a slight chance you can recover it by trying the Evita Unbricking thread, to be honest most attempts fail at the enumerating partitions step but it's worth a shot. Sorry I don't have a link but if you Google Evita Unbricking it should come up, it has WIP in the title somewhere. It requires a Linux OS, a virtual Linux setup should do the trick. If that doesn't work you'll need to get a jtag repair done (about $60 USD).
Sent from my Evita
timmaaa said:
Oh no. That's a recovery for the HTC One X. The Endeavoru part of the filename means HTC One X (it's the codename). The codename for the HTC One XL is Evita. There's a slight chance you can recover it by trying the Evita Unbricking thread, to be honest most attempts fail at the enumerating partitions step but it's worth a shot. Sorry I don't have a link but if you Google Evita Unbricking it should come up, it has WIP in the title somewhere. It requires a Linux OS, a virtual Linux setup should do the trick. If that doesn't work you'll need to get a jtag repair done (about $60 USD).
Sent from my Evita
Click to expand...
Click to collapse
Well I guess there's where I dropped the ball. haha.
Thank you for all your help, I'll try the first method and if all else fails I might just let go of the phone...
Hoping for the best.
If you don't want to have it repaired, you can sell it for parts (screen, speakers etc) and at least recoup a little bit a cash out of it.
Sent from my Evita
The fix semi worked. It's now rebooting constantly at the HTC white screen.
Hello to all i have been receiveing information a lot of times from xda but this is my first time i had to write i have a problem and i am not so good i can't fix it.
My HTC ONE X i jusrt rooted it unlocked the boot loader and isntalled a cyanogen cm10 but the boot image is looping and i tried erase chache davin and so on tried fastboot flash boot boot.img still the same my recovery is gone for some reason from the phone i have it only on the computer i tried almost everything i found but i cant even flash a rom i can upload i have this cyanogen 10 on my phone but it does not work however i install it so if someone expert can help me i will be very greatfull i am even ready if someone can write me on sky-pe ludoto922 i will be very greatfull i am also ready to give a little reward in paypal i haven't slept in 12 hours and i really need to fix it please someone expert give their opinions or write to me thanks!
Wow, firstly, punctuation.
Secondly, do you have the HTC One X (Endeavoru) or the HTC One XL / at&t One X (Evita)?
Sent from my Evita
timmaaa said:
Wow, firstly, punctuation.
Sent from my Evita
Click to expand...
Click to collapse
LOL i say the same thing.
timmaaa said:
Wow, firstly, punctuation.
Secondly, do you have the HTC One X (Endeavoru) or the HTC One XL / at&t One X (Evita)?
Sent from my Evita
Click to expand...
Click to collapse
I bought a brand new XL and it prompted me to update to the latest version, which was 4.2.2 but now I cant access my phone as mass storage. I have debugging on and no connect to pc option in settings. What can I do?
cowboysgz said:
I bought a brand new XL and it prompted me to update to the latest version, which was 4.2.2 but now I cant access my phone as mass storage. I have debugging on and no connect to pc option in settings. What can I do?
Click to expand...
Click to collapse
It no longer uses mass storage, it uses MTP now. You need to install HTC Sync Manager on your PC in order to access the sd card properly.
Sent from my Evita
timmaaa said:
It no longer uses mass storage, it uses MTP now. You need to install HTC Sync Manager on your PC in order to access the sd card properly.
Sent from my Evita
Click to expand...
Click to collapse
I already uninstalled and installed the drivers and still HTC SYNC wont recognize my phone. :/
cowboysgz said:
I already uninstalled and installed the drivers and still HTC SYNC wont recognize my phone. :/
Click to expand...
Click to collapse
That reminds me of a rare problem in windows. Sometimes it happens that when you uninstall usb devices, the usb.inf gets removed from the windows/inf folder, or something like that, so you need just a generic one and place it there again. After that the usb drivers for mass storage or MTP should get installed again by windows. If this shouldn't fix it you might want to search for similar problems.
hinogi said:
That reminds me of a rare problem in windows. Sometimes it happens that when you uninstall usb devices, the usb.inf gets removed from the windows/inf folder, or something like that, so you need just a generic one and place it there again. After that the usb drivers for mass storage or MTP should get installed again by windows. If this shouldn't fix it you might want to search for similar problems.
Click to expand...
Click to collapse
Yea I tried everything but fortunately I found out I can access my SD card through airdroid. Pretty good solution in case some one has the same problem.