Related
Ok guys, new to the forums but this problem has had me fully occupied for the last 6 hours and I feel like I have tried everything. I had cm9 alpha 12, and went to flash TrickDroid v5.0, something happened and I'm currently stuck in some wierd bootloop/soft brick. I had access to CWM but my SD card wouldn't mount and my adb push attempts didn't do anything, for reasons I don't know why. My phone would start up into the wierd trickdroid bootup and last for like 30 minutes. I tried the solution of another thread on how to fix a bootloop/ softbrick, but now I dont have any CWM access and I can only access the bootloader or the endless bootup screen. I tried using the all in one tool to flash the CWM again but it just restarts it and puts it back into the bootup, and when i restart to go to bootloader to acess the recovery, it goes back to bootup. Every solution I try makes my problem worse, and to top it off I cant turn my phone off and keep it off because it will just start back up. Thanks.
Edit: Problem fixed. Downloaded the original all in 1 tool for htc one s, plugged phone into comp went to fastboot and with the tool flashed the phones stock recovery. I reset to factory defaults and cleared storage with it from the bootloader. After that, I flashed clockwork mod recovery again and my SD card was able to be mounted and accepted files from my adb push, and I reflashed cyanogenmod. Wuzzah!
milesmarrero said:
Ok guys, new to the forums but this problem has had me fully occupied for the last 6 hours and I feel like I have tried everything. I had cm9 alpha 12, and went to flash TrickDroid v5.0, something happened and I'm currently stuck in some wierd bootloop/soft brick. I had access to CWM but my SD card wouldn't mount and my adb push attempts didn't do anything, for reasons I don't know why. My phone would start up into the wierd trickdroid bootup and last for like 30 minutes. I tried the solution of another thread on how to fix a bootloop/ softbrick, but now I dont have any CWM access and I can only access the bootloader or the endless bootup screen. I tried using the all in one tool to flash the CWM again but it just restarts it and puts it back into the bootup, and when i restart to go to bootloader to acess the recovery, it goes back to bootup. Every solution I try makes my problem worse, and to top it off I cant turn my phone off and keep it off because it will just start back up. Thanks.
Click to expand...
Click to collapse
lol, meant to "quote" not "thanks".
Can you fastboot a new recovery?
Did you do a full wipe coming from CM9 to TrickDroid
Well I can't access the phone from usb on my computer (still takes charge though), so I don't think I can flash a recovery thru fastboot (I'm not too experienced though). From cm9, I wiped all and flashed trickdroid + tweak set, then it just stat their at home screen. CMW being lost occurred later.
Im in the same situation rght now. I have trickdroid and I went into my tweaks to set them back to their original setup...so removing all of the options I chose before when I used the tweaks for the first time. When I rebooted my phone it just hangs on the HTC screen. I can get into recovery and I tried reinstalling trickdroid but its still getting stuck. Not sure what to do at this point. I don't think I can put a recovery file on this since I can't connect it to my computer.
Hopefully someone can help us.
But the thing is I can't access recovery. I try to flash it again with the all in 1 tool and it won't work. It says it went through, but accessing it doesn't work.
If its recognised by USB when plugged in computer just run an ruu that's my solution all The time lol
Sent from my HTC One S using xda premium
Ok i somehow managed to get TWR on my phone, but still unable to mount the SD. How do I run the RUU? I downloaded it, but the instructions are flawed I think
Connect with USB to.computer go into faatboot USB then run ruu on pc
Sent from my HTC One S using xda premium
Well I thought the RUU was going to work, but it just stops at the HTC and gives me an error saying I can't. What now?
Ok currently, I relocked my bootloader in an attempt to do the RUU, but I get a 155 Unknown Error up doing such, using the TMOUS 1.53 ruu... other places I have seen say something about returning to the stock img etc, but I'm quite stuck. Any advice appreciated
htc one s stuck in bootloop almost unresponsive
hey guys, got a brain teaser for you.
i have a tmobile htc one s, unlocked, rooted using all in one htc tool, been at it for two days now. im stuck on the boot screen showing its unlocked, i used to be able to get into the boot loader screen but now it seems ive dead ended. ill hold any combination of power and vol up/down, the keys flash for 10 sec and the screen flashes once, i let go and it reboots, keeps that htc screen, after 20-30 sec goes black. my pc doings like it detects a device but i cant locate it. ive used adb and the htc all in one unlock tool trying to get any kind of os to launch.
Shortly before this i was able to go into the boot loader, clear and master reset the files and cache, and search for the rom zip, thus never allowing me to flash. on a journey to place this in the phone through various combinations of the all in one, adb push, and everything else i found on youtube, countless forum posts, i seem to be in a deeper hole now.
I ultimately want to end with a cm10 nightly on my tmo htc one s. I have never done this to a phone without a sd card. i come to this community humbly seeking any and all advice. thank you.
Hello and thanks in advance, FIRST THINGS FIRST I have searched and have spent close to 48 hours reading and attempting to resolve this through KDZ_UPD and Reflashing CM7. Im having trouble with my phone trying to reflash the V21E baseband using KDZ. When i launch KDZ software update it only looks on port 1 and 2 then I get the "Phone Was Not Found" error. I powered off one day and pulled the battery then reset to find the "No Service" and ? for my battery. I was using CM7 for about Two months prior without any problems when this happened. Now i am currently back to stock 2.3.3 with stock recovery. From what i understand when i hold both volume buttons i should see three items pop up in my device manager however i only see nvidia usb boot recovery yada yada yada.... and that is only when i hold both volume buttons. While holding the volume down button it goes into S/W update but nothing in device manager ...... does this mean its bricked (I know some people say its not possible but not possible bad luck runs in the family) and if not how would i go about getting it to connect?
P.S. I have tried several different machines some xp pro(and a vm) and some win 7 ultimate, and several different cables on each...
Please help and offer some advise before i loose my marbles!
Thanks in advance
Also if this is in the wrong place i apologize i didn't want to resurrect an obsolete thread.
for ****s and giggles, click on the "show hidden hardware" checkmark within the device manager. Maybe there are borked and need to be removed / reinstalled on the XP install?
New2my8125 said:
for ****s and giggles, click on the "show hidden hardware" checkmark within the device manager. Maybe there are borked and need to be removed / reinstalled on the XP install?
Click to expand...
Click to collapse
Nothing there out of the usual... thanks for the quick reply. do you think I'm bricked?
Ok so i had somewhat of a breakthrough... i connected my phone and it found the lg port 4 under device manager.
So i started KDZ then about half way through it disconnected...... sending a bunch of authentication errors and corrupting my V21E_00.kdz file...
now it wont connect through any cables i try.... any thoughts?
For readers with input I am in a similar situation but am getting the bootloader up and LG logo but am also unable to enter recovery... so advice pertaining to the OP prior to the device going link dead is also valuable and sought after.
Sent from my SGH-T959V using xda premium
Ok for reasons unknown i had a brilliant idea which worked..
I had an mp3 player years ago that for some reason i would not connect to the computer unless (dont ask me why) I would put it in the fridge or freezer for a few minutes.
Anyways i figured id try this and it worked. all 3 devices in device manager popped up, set the cpu priority for KDZ to high and flashed the baseband!
Booted up, just fine however, i reboot the device and now i am in the same boat with the no service. going to try to flash cm7 and see if anythings different...
Ok so i flashed cm7 and the baseband worked on first boot up but after restart it was unknown again..
Can anyone confirm this is probably hardware?
Thanks!
So I have ran into a big problem. Yesterday I installed CleanROM 6.0 R2 and everything seemed fine until I woke up this morning. My device was turned off so I charged it a bit and powered it on. It was stuck on the HTC boot screen so I decided to use TWRP to recover the ROM. The problem is it says the SD card is unmounted. I got careless and started trying to wipe the SD card, format it, etc. to no avail. Now I can no longer get into TWRP.
Does anyone have any ideas? I am not sure what to do anymore =(
Related post: http://forum.xda-developers.com/showthread.php?t=2187491
Just an update... tried using ruu and getting error 171, using 2 different PCs. Once it tries to reload boot loader the phone doesn't turn on at all. Manually made no difference. Nothing seems to work. And since relocking the bootloader instead of receiving the error mentioned on the top I get a "remote: signature fail". Something else strange is the HTC boot screen no longer appears, instead going straight into the boot loader.
I've gathered with further tinkering when a command needs to reboot the phone it doesn't do it. I'm now trying to unlock the boot loader again, all goes well until it reboots then nothing happens. It's like it fails to write anything. I think earlier when I messed with TWRP before it stopped working I genuinely screwed something up with the SD card.
Try to hookup the phone to a Windows PC, go to Device Manager, and see if you have the option to format the SD.
EDIT: Just saw here that your main problem is communication between the PC and your phone (which would also explain why you can't mount SD). Try to reinstall HTC Sync, and also try another USB port on the PC.
redpoint73 said:
Try to hookup the phone to a Windows PC, go to Device Manager, and see if you have the option to format the SD.
EDIT: Just saw here that your main problem is communication between the PC and your phone (which would also explain why you can't mount SD). Try to reinstall HTC Sync, and also try another USB port on the PC.
Click to expand...
Click to collapse
The only thing I see listed is "My HTC" no option to do so. If you have anymore ideas please let me know!!
USBDeview
use this software to uninstall all the devices you think are related to your phone. it doesn't physically remove the drivers it will just allow your computer to reconfigure them, see if that helps. even if it doesn't it is a great utility to keep around.
DvineLord said:
USBDeview
use this software to uninstall all the devices you think are related to your phone. it doesn't physically remove the drivers it will just allow your computer to reconfigure them, see if that helps. even if it doesn't it is a great utility to keep around.
Click to expand...
Click to collapse
Hmm, messed around with it a bit, still no luck.
Okkoto said:
Hmm, messed around with it a bit, still no luck.
Click to expand...
Click to collapse
once you uninstalled devices and then replugged in phone how many drivers did it try reconfiguring? did you get any errors?
DvineLord said:
once you uninstalled devices and then replugged in phone how many drivers did it try reconfiguring? did you get any errors?
Click to expand...
Click to collapse
It reconfigured Android 1.0 (My HTC) and QHUSB_DLOAD when I try running the RUU software again.. Something worth mentioning is I've tried 3 different PCs all with HTC sync installed.
Okkoto said:
It reconfigured Android 1.0 (My HTC) and QHUSB_DLOAD when I try running the RUU software again.. Something worth mentioning is I've tried 3 different PCs all with HTC sync installed.
Click to expand...
Click to collapse
remember htc sync is pretty much useless always disable it, all you need are drivers. if u have htc sync installed disable or close it before doing anything important.
DvineLord said:
remember htc sync is pretty much useless always disable it, all you need are drivers. if u have htc sync installed disable or close it before doing anything important.
Click to expand...
Click to collapse
It's not open or anything. At first I just had the basic HTC drivers but been told to have the sync software installed. Either way I'm beginning to think the memory is faulty now, have messed with this thing for to long...
As the title says, RUU attempts booting my phone but it never comes back on. Even selecting restart boot loader in fastboot or a command it doesn't power itself back on. I have read through other forums and nothing has worked for me yet.
EDIT: I should probably clarify fastboot usb WORKS. Ruu must see my phone considering it detects the ROM version and turns the phone off in attempt to reboot. Anything that I do that requires a reboot doesn't work. I have tried unlocking the bootloader again, everything is fine until it comes to rebooting then I must turn the phone on myself and nothing changes...... IT DOESN'T REBOOT ITSELF therefore seemingly nothing wants to work. And the HTC boot screen is gone??
More background information: http://forum.xda-developers.com/showthread.php?p=39046436#post39046436
What we're your steps exactly? Did you relock your bootloader
a box of kittens said:
What we're your steps exactly? Did you relock your bootloader
Click to expand...
Click to collapse
Yes I did through fast boot with the oem lock command. I've tried installing RUU with a Windows 7 laptop (has HTC sync software) and Windows 8 desktop (basic drivers). Both failed, tried using Windows XP/Vista in compatibility modes and running as an admin with the same results.
Error 171 is a connection error, meaning the RUU can't connect to/find your phone.
Try uninstalling HTC Sync, rebooting your pc, and installing it again. If you've got the Android SDK installed, be sure it's also fully updated.
iElvis said:
Error 171 is a connection error, meaning the RUU can't connect to/find your phone.
Try uninstalling HTC Sync, rebooting your pc, and installing it again. If you've got the Android SDK installed, be sure it's also fully updated.
Click to expand...
Click to collapse
No luck. And I believe it does see the phone in the beginning of the installation. It makes it reboot to the boot loader and that's where it loses the connection. The phone just isn't booting itself back up. I appreciate the reply, if you have anymore ideas please let me know.
Could be something got corrupted. Try redownloading the ruu. Does adb see the phone?
iElvis said:
Could be something got corrupted. Try redownloading the ruu. Does adb see the phone?
Click to expand...
Click to collapse
Re-downloaded RUU and still no go. And adb doesn't see my phone, will it on the fastboot menu? I'm not to familiar with it.
Does anybody else have some more ideas?
Okkoto said:
And adb doesn't see my phone, will it on the fastboot menu? I'm not to familiar with it.
Click to expand...
Click to collapse
No. If adb doesn't see it, fastboot won't either. Does the command "adb devices" (no quotes) show the device as connected?
It sounds like the connection might be working for a few things (like rebooting the phone, as you mentioned). But I still think a connection issue is the main problem.
redpoint73 said:
No. If adb doesn't see it, fastboot won't either. Does the command "adb devices" (no quotes) show the device as connected?
It sounds like the connection might be working for a few things (like rebooting the phone, as you mentioned). But I still think a connection issue is the main problem.
Click to expand...
Click to collapse
Fastboot does see it but adb does not. And what I mean by rebooting the phone in my last post is RUU attempts rebooting it from the boot loader which does turn the phone off but it stays turned off. I've used other commands to reboot the phone from the fastboot screen and those too turn off the phone then again it doesn't come back on like a reboot should do.
I have about completely gave up and going back to using a regular feature phone. I have watched a video about a jtag repair service and was wondering about that or just selling the phone as bricked on ebay.
Okkoto said:
I have about completely gave up and going back to using a regular feature phone. I have watched a video about a jtag repair service and was wondering about that or just selling the phone as bricked on ebay.
Click to expand...
Click to collapse
don't sell it as bricked since it is obviously not bricked. you could get more money just saying you dont wtf your doing and gave up on it. but ill buy it as a bricked phone =) ill give you 50 bucks.
DvineLord said:
don't sell it as bricked since it is obviously not bricked. you could get more money just saying you dont wtf your doing and gave up on it. but ill buy it as a bricked phone =) ill give you 50 bucks.
Click to expand...
Click to collapse
Well if it's not bricked then I sure wish somebody would lead me to the right direction. I have tried 5 different PCs (which all show as connected through fastboot) and they all came with the same error. I've tried everything I could possibly think of and I haven't seen anyone else with quite the same problem I'm having.
I still have not completely gave up and have already decided against selling it as "bricked". The bootloader still comes up so there is at least some hope.
i just had the same problem. the solution was simple - i switch usb-port from front one to the backside one which is directly on motherboard.
Okkoto said:
Well if it's not bricked then I sure wish somebody would lead me to the right direction. I have tried 5 different PCs (which all show as connected through fastboot) and they all came with the same error. I've tried everything I could possibly think of and I haven't seen anyone else with quite the same problem I'm having.
I still have not completely gave up and have already decided against selling it as "bricked". The bootloader still comes up so there is at least some hope.
Click to expand...
Click to collapse
when you say it shows connected through fastboot what do you mean?
how are you getting the device into fastboot - through recovery??
oh, and what was on your device before you tried loading the RUU?
kkm68 said:
i just had the same problem. the solution was simple - i switch usb-port from front one to the backside one which is directly on motherboard.
Click to expand...
Click to collapse
Yes this + if you're on a usb3 port try usb2. Also make sure you're using the cable that came with the phone as I understand other cables may cause issues like this. Also, avoid using a hub or usb extension.
Solution to error 171
I had the same problem and after many attempts I finally got it to work!
-Uninstall anything HTC related from your computer such as HTC Sync Manager and Drivers. Also delete any HTC folders from your program files.
-Make sure you leave the sdk and adb stuff that you downloaded.
-Connect your device via USB to your computer and let it recognize it. It will automatically install default drivers.
-A pop-up asking to install HTC Sync will appear, just ignore it.
-Make sure you set Fast Boot OFF on your phone, and Debugging ON.
-Leave your phone ON and run the RUU set up.
-Then follow the steps on the wizard and everything should work just fine!
diegoyabishh said:
I had the same problem and after many attempts I finally got it to work!
-Uninstall anything HTC related from your computer such as HTC Sync Manager and Drivers. Also delete any HTC folders from your program files.
-Make sure you leave the sdk and adb stuff that you downloaded.
-Connect your device via USB to your computer and let it recognize it. It will automatically install default drivers.
-A pop-up asking to install HTC Sync will appear, just ignore it.
-Make sure you set Fast Boot OFF on your phone, and Debugging ON.
-Leave your phone ON and run the RUU set up.
-Then follow the steps on the wizard and everything should work just fine!
Click to expand...
Click to collapse
I have a similar problem with my HTC One. I am stuck in the bootloader and any action I take leads straight into a boot loop. If I try to reboot, reboot-bootloader, go into recovery (twrp), or factory reset it goes into a boot loop. Also I can't lock the bootloader and flashing my recovery doesn't help, even though it says its a success. I've tried three computers and deleted and reinstalled drivers but still the computers only find my phone in fastboot usb and can't find it using adb.
This solution above won't help me since I can't get my phone on for the life of me. I tried running RUU and All-in-One Toolkit but no luck. RUU fails finding the bootloader since my phone gets stuck in its boot loop. I am fresh out of ideas so any other ways to fix this issue would be greatly appreciated.
BTW I found my phone is this condition when I pulled it out of my pocket. I never installed custom ROMs on it. It is unlocked and rooted though running 4.2.2 (3.05.651.6) hoot 1.55. The only thing I can think of is that an OTA update got pushed to my phone and bricked it. That or for some strange reason something went wrong with phone from the rooting process after two weeks of it working perfectly.
jondon156 said:
I have a similar problem with my HTC One. I am stuck in the bootloader and any action I take leads straight into a boot loop. If I try to reboot, reboot-bootloader, go into recovery (twrp), or factory reset it goes into a boot loop. Also I can't lock the bootloader and flashing my recovery doesn't help, even though it says its a success. I've tried three computers and deleted and reinstalled drivers but still the computers only find my phone in fastboot usb and can't find it using adb.
This solution above won't help me since I can't get my phone on for the life of me. I tried running RUU and All-in-One Toolkit but no luck. RUU fails finding the bootloader since my phone gets stuck in its boot loop. I am fresh out of ideas so any other ways to fix this issue would be greatly appreciated.
BTW I found my phone is this condition when I pulled it out of my pocket. I never installed custom ROMs on it. It is unlocked and rooted though running 4.2.2 (3.05.651.6) hoot 1.55. The only thing I can think of is that an OTA update got pushed to my phone and bricked it. That or for some strange reason something went wrong with phone from the rooting process after two weeks of it working perfectly.
Click to expand...
Click to collapse
Nobody here can help you as we don't have any experience with your device. You'd be much better off asking in the HTC One forum which you'll find here:
http://forum.xda-developers.com/htc-one
Sent from my Evita
Heisenberg said:
Nobody here can help you as we don't have any experience with your device. You'd be much better off asking in the HTC One forum which you'll find here:
http://forum.xda-developers.com/htc-one
Sent from my Evita
Click to expand...
Click to collapse
hi all..
facing same problem with HTC Desire 816 n 4g... have anyone got any solution??
plz pass it..
thank you
Hey everyone. So everything was good for the last couple of days as I was on JellyBAM 6.6.0 evita. This morning after charging my phone I go to open it, view some websites etc. Phone reboots by itself, goes to lockscreen. I try unlocking my lockscreen everything good for about 10 seconds. Try to open facebook up, and boom phone goes black and will not turn on. I know for a fact that is 100% charged as when I woke up I checked the battery as I usually do to see if it charged or not.
I am pretty sure I am on Hboot 1.09 or less as I bought the phone close to the release date. Any thoughts because its weird how I cant turn even turn it on or have a LED light show up when it charges.
Thanks in advance
EDIT: Ok somehow my phone just turned on by itself and I took the opportunity to go into TWRP. Tried restoring but to a previous backup. Became stuck in boot screen. Went back into twrp tried to wipe the system and factory reset but somehow it says failed and that its not able to mount storage or anything. All of my data is gone now for some reason and it says no OS is installed. Do I have to RUU back again?
have you tried getting into bootloader by holding volume down and power? or a hard reset by holding power button for like 30 seconds
Sent from my HTC One X using xda premium
NerdFurgison said:
have you tried getting into bootloader by holding volume down and power? or a hard reset by holding power button for like 30 seconds
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Yeah I forgot to mention I have tried getting into bootloader using the volume down + power process along with holding the power button. Nothing is working.
This phone has well-known power management issues. Sometimes the battery stats get corrupted and the phone thinks the battery is dead when it isn't. Unfortunately, this sometimes results in a brick.
Plug into your PC and see what pops up in Device Manager. If you get QHUSB_DLOAD, you've been bricked. However, this may be fixable since you're on 1.09.
Ok somehow my phone just turned on by itself and I took the opportunity to go into TWRP. Tried restoring but to a previous backup. Became stuck in boot screen. Went back into twrp tried to wipe the system and factory reset but somehow it says failed and that its not able to mount storage or anything. All of my data is gone now for some reason and it says no OS is installed. Do I have to RUU back again?
Additionally, under device manager it comes up as unknown. I am going to install the ADB drivers for Windows 8 and see if that does anything
Zobabe said:
Ok somehow my phone just turned on by itself and I took the opportunity to go into TWRP. Tried restoring but to a previous backup. Became stuck in boot screen. Went back into twrp tried to wipe the system and factory reset but somehow it says failed and that its not able to mount storage or anything. All of my data is gone now for some reason and it says no OS is installed. Do I have to RUU back again?
Additionally, under device manager it comes up as unknown. I am going to install the ADB drivers for Windows 8 and see if that does anything
Click to expand...
Click to collapse
Well, wiping /system and factory reset means the OS is erased. Could be the sdcard got corrupted. You'll need to reformat it.
Good news is you're not bricked; its just a matter of getting the software in order.
iElvis said:
Well, wiping /system and factory reset means the OS is erased. Could be the sdcard got corrupted. You'll need to reformat it.
Good news is you're not bricked; its just a matter of getting the software in order.
Click to expand...
Click to collapse
Ok so should I follow like this.
Download HTC drivers
Download 1.71 RUU
Done?
Because right now my computer does not recognize my phone. Installing the htc sync and the drivers hasnt made my computer (windows 8) to recognize my phone.
Zobabe said:
Ok so should I follow like this.
Download HTC drivers
Download 1.71 RUU
Done?
Because right now my computer does not recognize my phone. Installing the htc sync and the drivers hasnt made my computer (windows 8) to recognize my phone.
Click to expand...
Click to collapse
Did you try formatting in twrp? Ruu'ing might be overkill here. Can adb see the phone even if windows can't?
Zobabe said:
Ok so should I follow like this.
Download HTC drivers
Download 1.71 RUU
Done?
Because right now my computer does not recognize my phone. Installing the htc sync and the drivers hasnt made my computer (windows 8) to recognize my phone.
Click to expand...
Click to collapse
I had a similar problem last night with a "missing" SDcard in TWRP. Thankfully, I found a utility that you can run through fastboot that will restore the SDcard without ruu.
HOWEVER...that utility and website link that I found it on are on my computer at home...and I'm not at home
Although, I did find the utility through a google search.
Let me know if you find it. If not - I'll find the link when I get home.
iElvis said:
Did you try formatting in twrp? Ruu'ing might be overkill here. Can adb see the phone even if windows can't?
Click to expand...
Click to collapse
I am having trouble downloading ADB drivers atm. Trying to find an article that explains it. Kind of a noob at this type of stuff. As for formatting, I dont see an option in TWRP.
razorc03 said:
I had a similar problem last night with a "missing" SDcard in TWRP. Thankfully, I found a utility that you can run through fastboot that will restore the SDcard without ruu.
HOWEVER...that utility and website link that I found it on are on my computer at home...and I'm not at home
Although, I did find the utility through a google search.
Let me know if you find it. If not - I'll find the link when I get home.
Click to expand...
Click to collapse
If you could please link it to me, it would be greatly appreciated. Thanks
I dont know if this matters but I factory resetted from bootloader in the beginning after I was able to turn on my phone. Maybe everything got wiped because I did that?
Does anyone know how I can get windows to recognize my phone because I have looked at several guides on google and nothing is working for me.
Thanks
Zobabe said:
If you could please link it to me, it would be greatly appreciated. Thanks
Click to expand...
Click to collapse
Here is that link I was telling you about.
Follow the instructions in the cmd. There should be only two steps.
Good luck!
http://forums.team-nocturnal.com/sh...ountable-internal-storage-on-the-HTC-One-X-XL
razorc03 said:
Here is that link I was telling you about.
Follow the instructions in the cmd. There should be only two steps.
Good luck!
http://forums.team-nocturnal.com/sh...ountable-internal-storage-on-the-HTC-One-X-XL
Click to expand...
Click to collapse
in order to this though, my computer has to be able to recognize my htc one x. I cant even get it to recognize. any tips?
Zobabe said:
I dont know if this matters but I factory resetted from bootloader in the beginning after I was able to turn on my phone. Maybe everything got wiped because I did that?
Does anyone know how I can get windows to recognize my phone because I have looked at several guides on google and nothing is working for me.
Thanks
Click to expand...
Click to collapse
yea, factory reset in bootloader is bad. never do it again unless you are completely stock.
DvineLord said:
yea, factory reset in bootloader is bad. never do it again unless you are completely stock.
Click to expand...
Click to collapse
haha yeah I realized that once I did it and read it in the sticky in the android development section. Do you have any idea of how I could get windows 8 to recognize my htc one x?
windows 8 is the last thing in the world i would let touch my computer. windows xp for life.
i heard alot of people having issues with win8 and usb 3.0 ports.